Skip to content
Team Nexa
All posts

Use case

The decision log: an institutional memory for leadership decisions

Six months after a big call, few teams can say exactly why they made it. How decision memos become a record of options, evidence and approvals that long-serving and new executives can both use.

2 min read

  • Strategy

Ask a leadership team why they chose one pricing model over another, or why they delayed a market launch last spring, and you often get several different answers. The people who argued for each option remember their own side. The evidence lives in a deck nobody can find. The person who made the final call may have left.

That is expensive. Teams reopen decisions they have already made, repeat analysis that already exists, and sometimes reverse a good call because nobody remembers the reason behind it.

What each entry holds

  • The question and the decision, in one or two sentences.
  • The options that were on the table, including the ones turned down, with the tradeoffs the team saw at the time.
  • The evidence behind it, with links to the source figures as they stood on the day of the decision.
  • The assumptions the decision relied on, kept separate from the facts.
  • Who approved it, when, and which actions followed.

How the log builds itself

When the Strategy agent drafts a decision memo and the leadership team approves an option, the memo becomes an entry in the log. Nobody has to write minutes or file anything. Decisions made in a meeting without a memo can be added from the meeting notes, and the agent asks the owner to confirm the details before they go in.

Onboarding new executives

A new CFO or CRO usually spends their first months learning why things are the way they are. The log shortens that. In the first week, they can read the twenty decisions that shaped the current plan, along with the options that were rejected and why. They join the conversation with context, instead of reopening settled questions by accident.

Where to start

Most teams start by logging new decisions from the day the Strategy agent is connected, then add the handful of past decisions people still argue about. Those are usually the ones most worth writing down.

Keep reading

All posts
  • Use case

    From brief to action: how the agents handle follow-through

    A good brief tells you what changed. Then someone still has to send the email, update the plan and chase the owner. Here is how the agents take that part off your plate, with your approval at every step.

    • Strategy
    • Finance
    • Revenue
    • Operations

    2 min read

  • Use case

    Linking the product roadmap to revenue and cost

    Roadmap reviews talk about features. Board meetings talk about revenue. The Product & Tech agent connects the two, so you can see what each big bet is worth and what it costs.

    • Product & Tech
    • Revenue
    • Finance

    2 min read