If every decision comes back to you, you have built a queue.

Start by explaining what needs deciding.

In the podcast, I describe my frustration with a call where we went round several times and still reached the same conclusion we had early in the discussion. The length of a call itself does not bother me. Time passing without a clearer basis for a decision does.

Fredrik stresses first defining the problem, examining possible causes and considering different solutions. That gives the person helping make the decision something concrete to assess. We need not start by trying together to work out what the question even concerns.

That preparation makes a big difference in a team. Say what you want to achieve, what you have seen and why you propose a particular route. Then others can contribute something that actually moves the reasoning forward.

Responsibility needs room to do the job.

When I enter a partnership, I want us to be clear about who is responsible for what and why. If I am brought in for marketing and e-commerce, there also needs to be room for the team and me to work within that responsibility.

At the same time, I do not want to direct things where someone else has the expertise. In the episode, I use product development as an example. I want a well-founded proposal from the person who knows the field, to understand the important choices and to let that person continue the work.

If everyone participates in every detail, the person who knows the subject still has to wait for the rest. Decide what that person can settle alone and which choices you need to understand together. Otherwise the company pays for expertise sitting in a queue.

I want to change my mind for a good reason.

I say in the conversation that I like being challenged when there is data behind it. Pitting gut feeling against gut feeling easily becomes a discussion of who carries the most weight in the room. That is rarely the best use of our different perspectives.

An objection becomes more interesting when we can investigate it. What have you seen among customers? What do the results show? Which hypothesis do you want to test, and what would change your mind? Then there is something to work on together.

That does not mean we always have a finished answer before deciding. In an early-stage company, we often need to test to understand more. But a clear experiment can give us better evidence than another round of everyone repeating what they already thought.

Not every detail needs the same amount of discussion.

In the podcast, I distinguish business-critical matters from others. I also talk about early-stage companies needing to move quickly, while the consequences of a mistake can grow as the business expands.

That is an important nuance in the argument about pace. An improvement we can test and adjust need not always get the same treatment as a decision that binds the company for a long time or affects many people. We need to understand what is actually at stake.

Fredrik also describes rules for when different AI roles should keep discussing and when the work should stop. There too, someone needs to decide which questions require more scrutiny and when the evidence is enough to proceed.

• Make the question and responsibility clear.
• Decide what needs reviewing before you proceed.
• Follow the outcome so the next decision can improve.

A partner should bring energy to the work.

I am drawn to people who want to build something, can collaborate and bring energy into the room. That is part of how I think about new projects. Expertise matters a great deal, but so does how we can work together over time.

To me, trust means we have agreed why we need one another’s help and then let that shape everyday work. We can share information, ask sharp questions and learn from what happens without reopening the entire division of responsibility every time.

In the episode, I return to needing to let go of certain parts when bringing in others with relevant experience. That is not the same as ceasing to care about the company. It gives you more opportunity to put your time where it makes the biggest difference.

Use the pace to understand what the customer encounters.

When Fredrik asks what I would first examine in a new project, I start with the whole journey. How does the customer find us? What does she buy? Does she return? If something fails, we need to keep asking questions along the way.

We discuss questions after purchase and to people choosing to leave the site, among other things. An answer can provide a clue an overall figure misses. The customer may have heard about the product elsewhere, felt unsure about delivery or encountered something broken.

Clear responsibility leaves more time for those customer questions. Choose one, find out what happens and give the person responsible room to make the change. The next check-in can concern the outcome.