profile

Spark to Hack ✧

Decision Fatigue? Let’s Cut Through the Noise Together StoH#26

Published about 2 months agoΒ β€’Β 3 min read

Hello !

​

If you feel you have not achieved what was planned 😱 at the end of the quarter or the year, here is an actionable way to improve your team's performance. Making better and faster decisions.
​

​

"In any moment of decision, the best thing you can do is the right thing, the next best thing is the wrong thing, and the worst thing you can do is nothing."
Theodore Roosevelt

Get comfortable for your 5 minutes of sparks to hack.

​

✨ Spark

​

✏ Mindset reset: more risks lie in no decision

​

"A" decision is better than "no" decision. Action is better than inaction. A wrong choice is better than no choice. (thanks, Nicolas Cole, for the summary)

This is why improving how you and your team make decisions is critical.

✏ Reversible vs irreversible decision: the analogy of the door

​

In 2016, Jeff Bezos shared his big idea to make Amazon even more successful. He focused on making decisions faster: we should not wait to know everything (90-100%) before we decide. Waiting too long can stop new ideas from happening.

Bezos suggested looking at decisions in two ways:

  • Type 1: one-way door: Big decisions that you can't change easily. These should be made carefully.
  • Type 2: two-way doors. These are smaller decisions that you can change or undo. They should be made quickly to keep things moving.

​

​

At Amazon, they call this one-way door = type 1 (If you walk through and don’t like what you see on the other side, you can’t return to where you were before) or two-way doors = type 2.

Type 2 decisions can and should be made quickly by high-judgment individuals or small groups. However, as organizations grow, they seem to tend to use the heavy-weight Type 1 decision-making process on most decisions, including many Type 2 decisions. According to Jeff Bezos, this results in slowness, unthoughtful risk aversion, failure to experiment sufficiently, and consequently diminished invention.

​

✏ Consequential vs non-consequential :

​

So besides the risk (type 1 or type 2) we take by making a decision, another consideration is the impact. It is consequential (significant impact) or not (low impact).

​

​

So, the first thing we should do as a team is assess which decisions we are considering:

  • All the inconsequential decisions can either be made quickly or delegated to one individual only or to another team.
  • Consequential and irreversible (1-way door - the type 1 from Jeff Bezos): take your time and collect as much evidence as possible (here, we assume experimentation is not possible - this situation is scarce if we are honest).
  • Consequential and reversible: the place to bring agile and experimentation to help you decide.

​

✨ Hack

​

✏ Off-line decision making

​

For all the inconsequential decisions, leverage offline decision-making. For example, using video to share a report or a prototype and ask for feedback and decisions is powerful.

I do more than 15 videos per week, using Loom (today more than 310 videos)

​
β€‹βœ Use the right questions

In meetings, here are 3 questions that will help (force πŸ˜‰) you to decide or prioritize :

What are the risks and impacts of this decision?

What are the risks or the opportunities we will miss by not making a decision now?

What else do we need to make a decision? If you stop gathering helpful information and there is no prospect of any on the horizon, make the decision.
​

✏ Avoid vague decisions - allocate more time

​

A vague or wavering decision opens the door to various interpretations, which will lead to confusion, doubts, and questions.
​

Β½ DECISION = CHAOSΒ²
​
Agnes Brunet from Olivier Bas

​

If you feel hesitation creeping in, even when you have all the information you need to make a decision, force yourself.
Make a decision. Stand by it.

For that, make sure to keep time allocated to decisions: I like to force my teams to keep the last 15 minutes per hour of meeting to decide the next steps.

​

✏ Better structure your meeting

​

Structure your meeting by identifying when to decide versus when to share and interpret information and progress.

We call it the CAPTAIN meetings: Collect Analyse Plan.

​

Collect: Share what evidence has been gathered since the last meeting.

This could be interviews your team has conducted, insights from your sales or field teams, or the result of market research.

The aim is to have everything collected in one place and one meeting, ensuring a comprehensive view of the new data collected.

Analyze: Debrief, interpret, debate, and argue.

The more friction, the better! It signals that you are looking at the collected evidence from multiple angles and leveraging the diversity and minority interpretations of the insights within your team.

Plan and Decide: how does what you learned influence our current plan? Which new decision need to be made?

​

That's all for today!

​

We teach this structure in our online acceleration program BOOST for early-stage teams in healthcare based on the insights from more than 500 healthcare teams coached.
​
​​

​

​
See you in two weeks. Keep the spark alive, and be intentional :).

​

Hit reply to let me know if you liked this edition or if you tried these tips. I respond to every person who writes to me!

See you in two weeks. Keep the spark alive, and be intentional :)

Spark to Hack ✧

by Aurelie Moser

Hi, I'm AurΓ©lie, a professional coach and facilitator, specialized in innovation in healthcare and sustainability. I enable team and organization leaders in healthcare to increase the speed between an ideas discovery and significant investments. I bring creativity and disciplined methods with contagious energy and a smile as well as a team and system coaching approach. I have a No BlaBla, No Bulshit, and no Blingbling values. I am a entrepreneur / working Mum aware that I only have one life, so I want to make the most of it!

Read more from Spark to Hack ✧

Hello ! I started coaching in healthcare innovation 10 years ago. When I say "innovation," I do not mean only projects led by a professional innovation team but also, most importantly, by non-professional innovators. I am talking to leaders and teams in digital health, marketing, business excellence, medical, access, pricing, and innovation. I see a pattern of frequent errors when corporate teams start a new "innovation" project. I will list the main mistakes and share my top five easy tips...

26 days agoΒ β€’Β 5 min read

Hello ! Spring is here in Basel, Switzerland. It's so lovely to see the color and the smell. Last week, I reached over 10 million public funding allocation application reviews from startups and academic projects. This is the occasion to summarize the leading mistakes teams make when developing a new solution. By solution, I mean a product (launch a complex and costly new oncology combination), a process (be ready to deal with the latest European legislation on HTA), or a service (AI-based...

2 months agoΒ β€’Β 4 min read

Hello ! Today, we will dive into how to best articulate the value of your strategy, product, or service. I will share the most common mistakes and exercises I love to do with my teams so you can save time and make sure you develop something people will like. "Clear is kind. Unclear is unkind."" Brené Brown Get comfortable for your 5 minutes of sparks to hack. ✨ Spark ✏ Why this is critical You don't want to develop a service or product nobody uses or buys? Let's see the 3 most common mistakes...

3 months agoΒ β€’Β 4 min read
Share this post