Flow is a team sport

Every role can improve the build.

When we picture flow, we often picture one person, headphones on, deep in the zone. But the flow that builds meaningful things is a shared one. It is a team making the next useful handoff easier.

Look at the line of roles in the picture. Each one is connected to the next. Nobody is the whole chain.

Eight ways to contribute

• Problem framer. Names what is really going wrong.
• Designer. Shapes how it feels to use.
• Developer. Turns the shape into something that works.
• Domain expert. Knows what is true in the real world.
• User researcher. Brings the voices of the people it is for.
• Security thinker. Asks what could go wrong, and who it could hurt.
• Communicator. Makes it understandable and welcoming.
• Tester. Finds what the rest of us missed.

You do not have to write code

You can define the problem. You can provide real examples. You can describe what good looks like. You can test the experience, check the language, and notice who has been left out.

Or you can ask the one question that stops a team from building the wrong thing. That question can save weeks, and it is often asked by the person who felt least sure about speaking up.

So speak up. Your role is part of the build.