Team-sponsored Build Days
Bring a small group inside one company together around work your people already own.
Plan a team session ↗BD Build Days / the enduring offer
Bring the work.
Build a better way.
A working session for work that should operate differently now.
Build Days help people use the Premise to Practice Method on one recurring workflow. The result is not a tool tour or a certificate. It is a tested work system, evidence from real use, and a clear next decision.
WAYS TO BUILD / 02SAME METHOD · DIFFERENT ROOM
Open Build Days
Join independently and build alongside people from different industries, functions, and points of view.
See upcoming dates ↗01PREMISE TO PRACTICETHE METHOD
Question it.
Build it.
Prove it.
The work stays close enough to reality that the awkward questions surface while there is still time to answer them.
- 01METHOD
Find the old premise
Name the outcome, the inherited path, and the assumption holding the current work in place.
- 02METHOD
Rewrite the work
Design a better path around what people and AI can do now. Keep the judgment. Remove inherited friction.
- 03METHOD
Build it close to reality
Create the smallest useful version that can survive real inputs, boundaries, and use.
- 04METHOD
Prove it in practice
Test the work, keep the evidence, and decide what deserves to happen next.
PRIVATE BUILD DAYS / TEAMS
Give your team a real piece of work to change.
A private Build Day creates a shared working language without turning the day into generic AI training. We scope one or more useful workflows, build against your operating context, and leave your people with working versions and proof they can inspect.
Plan a team Build Day ↗PUBLIC BUILD DAYS / INDIVIDUALS
Bring your own work. Build with a room full of different perspectives.
Public Build Days are open to independent participants and employer-sponsored individuals. You get the same build discipline plus the advantage of seeing how people in other industries frame problems, test assumptions, and make decisions.
Explore public Build Days ↗Leave with
the work.
- 01
One recurring workflow with a named outcome and owner
- 02
A working AI-supported version built around real constraints
- 03
Representative tests with observed results
- 04
Guardrails for review, escalation, data, and recovery
- 05
A 30-day operating plan for continued use
ONE REAL WORKFLOW→ONE TESTED SYSTEM