Scaleflow names four roles, and they are about responsibilities, not titles. A person can hold different roles on different initiatives, and people flow between them as an initiative evolves. The same engineer might authorInitiative AuthorThe person accountable for an initiative's context — they write and keep the Initiative Document honest. one effort and simply be part of the Team on another.

This is deliberate. Title-based org charts create silos — sales throws work to product, product throws it to engineering, and context leaks at every wall. Scaleflow names responsibilities instead, so that the question is never “whose job is this?” but “which responsibility does this belong to, and who is holding it right now?” The four roles below are the answer.

The Team

The multidisciplinary group doing the work and owning the weekly reality.

  • 2 to 9 people, multidisciplinary by design.
  • Full-time membership is preferred, but part-time is supported by design.
  • People can and should flow into and out of the Team across phases. A research-heavy inception phase needs different people from an engineering-heavy implementation phase.
  • Ideally not organised by titles — though in practice that is not always possible.
  • The Team commits to weekly demoable outcomes; individuals commit to the Team.

The Team is multidisciplinary so that the customer’s problem can be solved end to end without throwing work over a wall. Research, design, engineering, data, and the commercial side share one weekly reality rather than handing a baton between departments.

Example · #REALITY

The same initiative might run with a researcher and a designer doing most of the work in its inception weeks, then shift to mostly engineers once the solution is clear, then pull in someone from Sales or Customer Success as it heads towards launch. The roster is not fixed for the life of the initiative — it follows the work.

The Initiative Author

The person who gets an initiative off the ground.

  • Writes the initial Initiative DocumentInitiative DocumentThe PR/FAQ-shaped document where an initiative's context lives — customer, solution, plan, business case, and success metrics. and the initial Approach.
  • Makes sure the business case holds up and that funding — money and people — is secured.
  • Sources the initial Product BoardProduct BoardTwo or more stakeholders who see the team's weekly demo and coach it — the human in the loop, with no single lead. members.
  • Optionally hands the initiative over to an Initiative OwnerInitiative OwnerThe role accountable for keeping an initiative on track — owns the Initiative Document, the Approach, the team, and the board. once it is funded and shaped.

The Initiative Owner

The person who keeps the initiative honest once it is running.

  • Keeps the Initiative Document up to date.
  • Keeps The ApproachThe ApproachThe multi-week narrative roadmap — titled weekly outcomes ("The one where…"), each with a demo, planned backwards from success. up to date.
  • Alerts the chain of command early when the initiative is going off the rails.
  • Sources the Team.
  • Adjusts the Product Board if needed.
  • Owns central communication around the initiative.

The Product Board

Two or more people from the organisation who have a stake in the initiative or can supply needed context and experience. They are the home of the Board Meeting.

  • The board functions collectively as a coach to the Team. There is no single lead — that is deliberate.
  • It influences the trajectory of the initiative but does not own it.
  • It is the human in the loop — what makes teams deliver to people, not to ticketing systems.
  • Each member is available for at least one hour a week of high-quality interaction.

The board having no single lead is the whole point. A lone advisor becomes a single funnel — the bottleneck Scaleflow exists to avoid, where one person holds all the context and the Team simply executes. Two or more advisors, coaching collectively, keep context plural and decisions honest.

Across its members, a good board supplies four contributions:

  • The Specialist — has built something like this before.
  • The Critic — challenges the work and keeps it aligned with company values.
  • The Decision Enabler — breaks ties on budget, on unblocking teams, or on stopping.
  • The Customer Connection — from Customer Support, Customer Success, or Sales, bringing the customer’s voice into the room.

These are contributions, not chairs. A three-person board can cover all four; one member can carry two. What matters is that every contribution is present somewhere across the board, not that you appoint four named people.

In practice the board gives the Team context from its part of the organisation, direct feedback on the work, and organisational shelter and encouragement. The weekly hour each member commits is the floor, not the ceiling — it has to be high-quality, prepared attention, not a passive sit-in.

Example · #CONTEXT

On one initiative a Customer Success lead held the Customer Connection seat while also being the Critic — two contributions, one person. The point is that all four contributions are present across the board, not that you fill four named chairs.

People flow between roles

Roles are hats, not rank. As phases shift and initiatives layer over each other, the same people pick up and put down different roles. What stays constant is that each responsibility has an owner.