Practical guide · owner and manager

Give your manager a question they can investigate.

A useful brief defines the result, scope and return point. It leaves room for evidence to challenge the first explanation.

The complete loop

Preparation can be delegated; the decision right remains explicit.

RouteMapCommitReturn
01

1. State the result and the decision to follow.

Tell the manager what is not working and what choice the investigation should inform. For example: “We need more profitable completed orders. Compare whether sales capacity, approvals or specifications are limiting the flow before I decide on a hire.” State your present explanation as your view, not as the required conclusion. Include non-negotiable limits such as customer commitments or margin protection.

02

2. Give the work a boundary.

Choose a specific flow, period or set of cases. Name the review date and a manageable evidence budget. Identify the records and contributors the manager may access and what needs separate approval. Define whether the manager is only investigating or may run a particular test after owner approval. Avoid a brief like “fix operations”: it hides the decision, encourages uncontrolled scope and makes completion difficult to recognise.

03

3. Collect separate views before synthesis.

Ask contributors what they observed, what they think it means and what would change their view. A coordinator can describe missing specifications without deciding the staffing question. A sales colleague can describe customer response without asserting the cause of the approval queue. Gather useful input independently before exposing it to the owner’s or AI’s preferred account. Then compare the released views and keep their sources visible.

04

4. Ask for a recommendation with its limits.

The manager should return observations, competing explanations, missing evidence and the next check they recommend. Ask how the proposed action connects to the business result and what could disconfirm it. A polished summary without sources is not enough. AI may organise material or propose questions, but a person selects what enters the recommendation. Unresolved disagreement is part of the packet, not a failure to finish it.

05

5. Close the assignment with a return to reality.

The owner chooses the next move, defines the test boundaries and names the execution and review owner. Write the expected signal before acting. At the return date, compare the result, discuss exceptions and choose whether to continue or adjust. Tell contributors how their evidence influenced the choice. In an enabled company workspace, use the applicable permissions; public demo browsing does not create a company or delegate actual authority.

Your first company decision

Choose your next useful check.

See how the owner delegates preparation, the team contributes independent evidence, and a recorded result informs the next move. Then review the self-service paid company trial. No founder meeting is required.

Explore the team demo