Nate Lynch π€π»ππ€ retweeted
Education is not about knowing everything, itβs about understanding that there is always more to learn and discover.
My favorite niche basketball podcast is The Lowe Post. @ZachLowe_NBA does not have any merch to buy, so I made a t-shirt in honor of my fandom.
Pick one up for the NBA nerd in your life.
cottonbureau.com/p/RDJTYA/shβ¦
189
Nate Lynch π€π»ππ€ retweeted
Shark Week is a good time to remind you that the mayor from Jaws is still the Mayor in Jaws 2. This is why it is so important to vote in your local elections.
Letβs hear it for Alfred L. Cralle, the inventor of the ice cream scoop.
en.wikipedia.org/wiki/Alfredβ¦
127
Nate Lynch π€π»ππ€ retweeted
I love this litmus test for if a company has a strong brand or not.
From Seth Godin:
Nate Lynch π€π»ππ€ retweeted
thinking: βnaive and brilliant, and a great learnerβ is a killer combo - and the advantages of lacking a huge bias to traditional best practices is an advantage in startups. in big coβs with tenure-driven hierarchies, naΓ―vetΓ© tends to diminish credibility which is a real loss.
Nate Lynch π€π»ππ€ retweeted
βIn mathematics the art of asking questions is more valuable than solving problems."
- Georg Cantor (1845 - 1918)
Pro tip for corporate job seekers:
Request the high and low compensation dollar amount. (The salary band.)
Add those 2 numbers together
Divide by 2
Multiply by .9
That answer (90% of midpoint) is the max you can (typically) expect to negotiate for.
Good luck!
65
Nate Lynch π€π»ππ€ retweeted
There are only two ways to live your life.Β One is as though nothing is a miracle.Β
The other is as though everything is a miracle. βAlbert Einstein
Nate Lynch π€π»ππ€ retweeted
In 2007, I was 1 of 2 designers on Google Maps.
The app was growing like wildfire.
But it was becoming a cluttered mess β new features were being shoved into every pixel.
Hereβs the 4-step process we used to redesign Google Maps into one of the most loved apps in the world: π§΅
βββ
But first, itβs important to understand it is normal to build a product based on the underlying technical structure.
In 2005, Google Maps queried one of three databases for any search:
β’ Maps data
β’ Local business data
β’ Directions data
Not surprisingly, the first version of the website had three tabs, one for each of these databases: Maps, Local Search, Directions.
βββ
By 2007, Google Maps still wasnβt the dominant mapping application.
But it had hit PMF, its user base was growing quickly, and we were rapidly adding new content and features like:
β’ Satellite and Terrain views
β’ Streetview, 3D buildings, Traffic
β’ Editable map data, Reviews, Photos
β’ Transit Data
We were wedging new features into any space we could find in the UI.
It became clear the user experience was suffering and the product was growing increasingly complicated.
At that time, our VP, Marissa Mayer likened Google Maps to a Christmas tree that we kept adding more and more ornaments to until it started to fall overβ¦
We tried many different ways to rearrange the UI to accommodate new features.
Eventually we had to step back and rethink Google Maps based on what we knew was working, what brought people to the product, and what we believed the future might look like.
βββ
These were the 4 key steps we took to simplify the design of Google Maps to be the intuitive, durable, much-loved product that 1B people still use today:
1. Deconstruct
We wrote down all of the productβs current and upcoming content, features, and functionality and loosely grouped them into categories:
β’ Core features β The most common tasks people came to do (search, get directions, find businesses)
β’ Aspirational use cases β Tasks we wanted people to start doing (adding their own content, correcting inaccurate information, using Maps to explore new places, etc.)
β’ Global actions β Actions that impacted the entire page (print, share, save, etc.)
β’ Use case specific actions β Actions that were relevant only within a specific use case (eg while getting directions, being able to drag a route or add a destination)
β’ Related features β Things that werenβt a part of Google Maps at the time, but existed and were closely related. (eg transit information, business searches on Google.com)
βββ
2. Reframe
We leveraged a combination of user research, business goals, and our own intuition to make the product better, simpler, and scalable over time. We focused on understanding:
β’ What brought people to the product
β’ How they navigated through the product
β’ What was working well
β’ What flows were confusing
β’ What things were missing
β’ What information was valuable when
β’ What functionality was redundant
We emerged with several key points:
β’ βSearchingβ was the most pivotal task in Maps
β’ Searching addresses, businesses, parks, mountains, cities, etc could all be thought of as searching for βplacesβ
β’ Getting directions was important, but rarely happened between two specific addresses. Directions searches usually had a known start or end point, like home or work. It was also more intuitive to be able to search for directions by a place name e.g., Carmel Library rather than having to look up the address first.
β’ It was strategically important for people to be able to contribute content to Google Maps and to be able to explore the world around them.
βββ
3. Reconstruct
Based on what we learned, we then explored ways to reshape the product.
We held these general usability principles in mind:
β’ Entry points to core use cases should be prominent
β’ Flows within core use cases should be intuitive
β’ Common actions, interactions, and views should be consistent
β’ Contextual actions should be accessible when relevant
This is one exploration of clustering tasks and connecting relevant content:
Our explorations of how to reconstruct the site around peopleβs needs and flows led to several key design changes:
β’ There would be only one search box for everything
β’ Directions would live as a secondary feature
β’ Other features would appear in context (eg, transit became a mode within directions)
βββ
4. Scale for the future
This was 2007. We knew the product would continue to evolve, the information set would grow exponentially, and the feature set would continue to expand.
But by focusing on key use cases and folding information in to the UI where it was relevant, we created a framework to support future growth.
16 years later, Google Maps has continued to evolve, yet is still a simple, intuitive, much-loved product that 1B people use around the globe.
For more on design, follow @elizlaraki
This is a must-listen if youβre interested in the future of the employee experience. overcast.fm/+BlzGfX-94
32
Popcorn is the best snack. Shelf stable forever. Takes up a small amount of space. Is fun to make. You can top if with whatever youβre in the mood for.
Letβs hear it for popcorn.πΏ
1
39
Nate Lynch π€π»ππ€ retweeted
Barbenheimer. 2023 βπ½
#Barbie #Oppenheimer
If you lost [X] would you buy it again?
If not, do you even need it?
Subtraction. Subtraction. Subtraction.
36
Nate Lynch π€π»ππ€ retweeted
βThe one thing the world will never have enough of is the outrageous.β
β Salvador Dali, 1963



















