Jeff Bezos: “Any high-performing organization has to have mechanisms and a culture that supports truth telling”
As Jeff explains in the clip below:
“Truths often don’t want to be heard. Important truths can be uncomfortable, awkward, exhausting, challenging. They can make people defensive, even if that’s not the intent. But any high-performing organization—whether it’s a sports team, a business, a political organization, or activist group—has to have mechanisms and a culture that supports truth telling.”
And one of the things you have to do to support this kind of culture is talk about it:
“You have to talk about the fact that it takes energy to do that. And you have to remind people that it’s ok that it’s uncomfortable. You have to literally tell people: it’s not what we’re designed to do as humans… we mostly survive by being social animals—cordial and cooperative.”
He continues:
“You also want to set up your culture so that the most junior person can overrule the most senior person.”
And in every meeting Jeff attends, he always speaks last:
“I know from experience that if I speak first, even very strong-willed, highly-intelligent participants of that meeting will [wonder if their ideas are incorrect because they’re different from Jeff’s]… Ideally you try to have the most junior go first and then go in order of seniority so that you can hear everyone’s opinion in an unfiltered way… Because we really do change our opinions—if somebody you really respect says something, it makes you change your mind a little.”
Jeff also points out that a lot of the most powerful truths aren’t always based on data—they turn out to be hunches, are based on anecdotes, or are intuition-based:
“You may feel yourself leaning in. It may resonate with a set of anecdotes you have. And then you may be able to say: ‘something about that feels right. Let’s go collect some data on that and try to see if we can know if it’s right.’”
And lastly he discusses fighting inherent biases. For example, most companies usually have an optimism bias. As Jeff explains:
“If there are two interpretations of a new set of data—one is happy and the other is unhappy—it’s a little dangerous to jump to the conclusion that the happy interpretation is right. You may want to compensate for that human bias of trying to find the silver lining and say ‘that might be good, but I’m gonna go with it’s bad for now until we’re sure.’”
"Be a doer, not a talker."
Sam Altman proved it:
The doers won. The talkers lost.
Within a week of getting ousted as CEO of OpenAI:
— 710/770 employees threatened to quit
— Sam gets reinstated as CEO
— The board that ousted him gets fired.
Why would this be inevitable, according to Sam?
Because history belongs to these people:
The AI assistant travel app in @OpenAI's DevDay keynote today has got to be one of the most impressive live demos I've ever seen.
Brilliant presentation by @romainhuet + stellar design & engineering work by @simonpfish & @karoliskosas behind the scenes 👏
He's the man of the moment and he's soaking his third NRL Premiership all in! 🐾🏆
Supercoach Ivan Cleary isn't looking too bad after a massive night of celebrations.
HIGHLIGHTS: https://t.co/1q5zbxYaBN
📺 #NRLGF | Exclusive on Channel 9 & 9Now
#9News#NRL
Miro's $17.5B valuation isn't magic. It's flawless Product-Led Growth.
Here's what you can learn from Miro:
1. Just because a market is competitive doesn't mean there isn't a space for you
Miro has gone head-to-head with every big name in tech you can think of, from Microsoft to Notion. In a few short years, they’ve broken away from being nobody’s to category queens.
2. PLG companies don't need to start with the buyer or a single persona
Many SaaS companies focus on the customer who buys the product. Miro’s strategy focuses on the end user— building a product they love. This creates a pool of internal champions within the org.
3. The power of the freemium model is that it provides value first, receives money later
Miro keeps paywalls, credit card fields, and pricing pages away from onboarding. By offering unlimited teammates and core functionality for free, they reduce the barrier for teams to start using their platform—encouraging adoption and allowing users to experience the value without immediate cost. This drives their product-led sales engine.
4. If your product caters to individuals (single player) and teams (multiplayer), seriously consider two different types of onboarding
Individuals and joiners have different Aha moments and points of activation, meaning onboarding should focus on different things.
5. Artificial invitation mechanisms (i.e refer a friend) are not PLG
Sustainable growth from the product comes from built in in natural product-led acquisition. Don't start a startup where you need to go through someone else to get users.
6. Product-led sales should be a scientific approach to finding the “hand raisers” using our product
Lead generation at Miro is a continuously optimized and data-driven proccess for finding the 'hand-raisers'. These Product Qualified Accounts (PQAs) comes down to timing, account maturity, and the using the correct medium for reaching out.
This is from NASA. Good stuff. People alway say things like "we can't be agile because [regulatory, large, lives on the line]. If NASA can be agile, I'll bet you can.
Demystifying the ‘product design process’
There is no such thing as a ‘design process’. Instead, there are just a variety of tools that you should learn, suited to solving different problems at different times. Learn as many as you can (and maintain a curious mindset to learn new approaches in the future) and you’ll become a product design maestro in no time.
Brief overview
What is a design process anyway?
1. The Double diamond (Design Council)
2. Continuous discovery (Teresa Torres)
3. Triple diamond
4. Build Measure Learn
Just to name a few! Each have their own merits, and offer a similar but different take on product design, but fundamentally they help achieve the same end goal.
A useful way to think about the idea of a design process is to see it as a way of helping you do 2 things:
1. Determine a solution to the problem as quickly as possible (focus on speed)
2. Ensure you’re solving the right problem in the first place (focus on risk)
How a design process helps and hinders
A solid design process has its place in anyone’s toolkit or business process, and can often act as a very useful tool to align thinking across multiple teams or divisions in your organisation.
Think about the design process as a way of moving from problem to solution as quickly and effectively as possible:
- How long do you spend on each stage?
- How much effort do you invest?
- Who else do you involve?
- How much research is enough?
- What’s the best way of testing your idea?
- How do you learn as quickly as possible? How do you prioritise learning, i.e. via MVPs, user testing, forming great hypotheses, desirability testing.
What will actually help you figure out the most important thing allowing you to move on to the next step, rather than blindly following each step of your process just because it’s your process:
- Are stakeholder interviews relevant for this project?
- Do you really need to conduct primary research if this is already a well understood problem space?
- Do you need to work up detailed wireframes if we could test something with users in the same timeframe by pairing with an engineer?
- Could we run desirability testing using marketing channels/social channels to gauge customer appetite before we conduct lengthy research cycles or commit to code?
Thinking differently about the process of design
In essence, what we’re really talking about here is ‘design thinking’ rather than design process. While ‘design process’ may outline WHAT you’ll do, ‘design thinking’ focuses on WHY you’re doing it.
- What is the outcome from this stage of my process?
- What do I need to learn in order to move to the next step?
- How can I get to a conclusion as quickly as possible?
- What do I need to learn to de-risk this project or idea?
- How will this tool/framework/workshop/research help me determine the right solution?
Maintain a curious mindset
1. Try to understand a variety of tools from problem discovery, to prioritisation, ideation and validation. Only through understanding the pros and cons to each tool (the first part of Shuhari) will you begin to master them. Keep track of the tools you’ve learnt, log them somewhere helpful for future reference, even create your own toolkit for the future.
2. Understand what you don’t know. Even if you haven’t had a chance to use the tool itself, simply being aware of it is the first stage of learning!
3. Test out new tools. See your next design challenge as an opportunity to validate these new tools you’ve discovered and see if they help you get from A to B more efficiently, with a better outcome, than other tools you’ve used before.
Read the full post:
https://t.co/LL3JX4ohZv
Great work @riggydigs
#ux #ui #uxdesign #uidesign #userexperience #prototype #productdesign #designprocess #problemsolving #designthinking #designresearch #uxstrategy #uxresearch #usertesting #usabilitytesting #research #design #agile #mvp #business