Scaled events

Event Nº 01

Signal Inspection.

Signal Inspection is the entry point of the loop. It runs continuously in the background, since Align and Enable are always watching. Periodically the org takes an intentional pause and inspects the picture together.

What gets inspected

• Key product and business metrics. Are the numbers Align cares about moving in the right direction?
• Customer insights. What are users actually saying and doing? What’s coming back through productops, market research, and direct feedback?
• Strategic alignment. Has the goal shifted? Is current work still pointed at the right target?
• Prior-cycle retros. What did pods name as process gaps last cycle? Which of those have become process changes? Which haven’t?

Who’s in the room

Humans and AI at the same table. AI agents pre-process the signals, clustering them, summarizing, and surfacing anomalies, so the humans spend their time interpreting and deciding rather than reconstructing the picture from scratch.

What comes out

The output is product briefs. Each brief states a direction: what the org should pursue next, why, and what good looks like, anchored in the signals that justified it. Briefs feed straight into Scaled Planning.

Event Nº 02

Scaled Planning.

Scaled Planning takes briefs and turns them into committed work across pods. The goal isn’t a fully detailed spec. It’s enough shared understanding for pods to take it from there.

The work the PO teams do first

Value-stream-aligned PO teams pick up the briefs and run them through validation:

• UX design thinking. Is the problem the brief frames the right problem to solve? What does it look like from the user’s side?
• Value validation. Is the value real, and can it be measured? If we ship this, how will we know it worked?
• Mockups + architecture. UX and architecture work alongside the POs to shape the broad spec: enough fidelity that pods can plan, not so much that pods can’t decide.

The work the pods do next

With a broad spec in hand, pods come into the planning event to:

• Review incoming work. What’s being asked of this pod? Does the spec still match the pod’s read of the codebase and the user?
• Untangle dependencies. If this work depends on another pod, surface it now — not three weeks in.
• Pull commitments into the active backlog. Pods commit to what they’ll deliver this cycle and start the clock.

Event Nº 03

Flow.

Flow isn’t an “event” in the meeting sense. It’s the default state. We list it among the four events on purpose: most of the system’s time is spent here, building, not in scheduling meetings.

What pods do

Pods pull from their prioritized backlog, take a spec, turn it into a plan, and turn the plan into an implementation. The plan-to-implementation step happens fast on purpose. A short loop means feedback comes back early.

Why the loop is fast

Every iteration that ships gets feedback from real users and from AI evaluation. That feedback tells the pod whether the plan is correct. The longer the gap between iteration and feedback, the longer a wrong plan goes uncaught, and the more rework piles up.

Short loops pay off because every spec is written for both the human team and the AI agents. Shipping early closes the gap between what you meant and what the code actually does.

Event Nº 04

Scaled Review & Retro.

The closing event of every cycle has two halves. One looks outward at what shipped, the other inward at how the pod works. They feed different parts of the system on the next pass.

The two halves are why the loop closes properly. Without Review, Inspection runs on stale data. Without Retro, the process can’t learn.

The red button.

Both Align and Enable continuously review the signals coming through the system, and they don’t wait for the next event to react. When something needs to shift, either lane can throw the red button and direct a pivot.

How each lane uses it

Either way, the message lands in the next pod-level event and the work shifts. The red button is what stops the system from getting stuck on its own calendar.