Field Notes Archive
Daily Field Notes
46 field notes and counting. Short lessons drawn from the daily brief.
Make the Assumption Visible Before the Decision Moves
Learn how to make trade exposure, crisis practice, maintenance, and uncertainty easier to manage by naming assumptions early.
Build the Capacity That Carries the Promise
Build a capacity map for the people, information, funding, and safeguards that must carry growth forward.
Test the Condition Before Adding Scale
Find the demand, governance, infrastructure, or community condition that could defeat a plan before investing more effort.
Test the Condition Before Scaling
Test the condition behind a plan before scaling demand, finance, access, governance, or evidence.
Test the Bottleneck Before the Tool
Use a bottleneck check to strengthen a founder, education, community, or technology decision before scaling a tool or promise.
Find the Failure Condition First
Use a failure-condition check to strengthen a founder, education, community, or technology decision before adding more activity.
Test the Pathway, Not Just the Promise
Use a pathway check to see whether a research, policy, or founder initiative can produce a useful result after launch.
Check What Follows the First Result
Use a second-order check to see whether a policy, program, or founder decision improves the system after launch.
Make the First Failure Visible
Use one inversion check to make a service, institution, or founder-support system easier to enter and trust.
Check Who Shares the Reported Gain
Use one distribution check to see whether an efficiency gain improves output, pay, hours, or only the headline.
Name the Constraint Before Choosing the Fix
Use one listening check to separate the stated problem from the real constraint before you choose what to change.
Set one claim test before you act
Set one decision test before acting so a stronger signal only passes if your next move stays useful under pressure.
Test What Could Still Go Wrong
Turn one daily signal into one testable condition and decide only after evidence shows what would make your move fail.
Design your next move as a falsification test
Learn to turn one daily signal into a concrete test that can change your decision this week.
Test the Claim Before You Trust It
Learn to turn a promising signal into a test that can change your mind.
Check the Next Consequence First
Learn to test a promising signal by asking what second step it creates for people.
Check Capacity Before You Count Growth
Learn to test whether a promising growth signal has the capacity to become a result.
Check the Support Before Scaling
Check why promising signals need visible support before becoming durable results.
Check the Support Before Judging
Check the support system behind outcomes before judging effort, talent, or performance.
Find the Constraint First
Find the bottleneck that blocks progress before asking people to add more effort.
Make the Label Earn Its Work
Test whether a label, tool, grant, or pilot is backed by visible work.
Make the Promise Specific Enough to Test
Use one test to turn a broad promise into evidence-backed action.
Check the Map Before Acting
Use one reality check to make plans, dashboards, and support programs safer before people depend on them.
Name the Support System Before Growth Arrives
Use one support-system check to make a promising growth signal safer before pressure tests it.
Test the Bottleneck Before You Scale
Use one disconfirming question to expose the constraint most likely to break a plan before rollout.
Diagnose the System Before You Blame
Use a four-part check to separate harmful intent from bad rules, weak capacity, and hidden pressure.
Count the Work the Dashboard Hides
Add one missing-measure check before using a dashboard to judge workload, access, or system performance.
Ask Who Feels the Constraint First
Use frontline knowledge to spot second consequences before a product, process, program, or policy becomes harder to change.
Name What the Model Cannot See
Use rules, dashboards, and frameworks without hiding the people, limits, and operating conditions they affect.
Make Information Useful Before Decisions Close
Use a four-part check to turn options, feedback, public records, and reflection into better choices.
Move Help Into the Moment of Need
Move evidence, advice, and practice closer to the moment where people must decide, learn, serve, or adapt.
Check What the Number Leaves Out
Use metrics as maps: name what they capture, what they miss, and what observation would update the decision.
Sort the Signal Before You Act
Slow down around noisy movement and choose the right amount of process before acting.
Put Support Where the Work Happens
Lower the first barrier and place help inside the course, meeting, shift, or workflow where people already make decisions.
Make Agreement Concrete Before You Move
Turn broad words into clear facts, tradeoffs, owners, and next actions before pressure exposes false alignment.
Build the Buffer After the Start
Momentum can hide weak follow-through. Build the extra room, clear paths, and protected time people need after the first move.
Build the Bridge Before You Ask for More
Before asking people for more effort, identify the advisers, coordinators, trust, standards, and checks that make dependable action possible.
Name the Dependency Before It Becomes the Emergency
Service-minded leadership names quiet dependencies before they become urgent failures.
Build the Backup Before the Forecast Fails
Service-minded leadership builds backup capacity before pressure becomes crisis.
Build Support Close to the Work
Service-minded leadership makes support close enough for people to use.
Know What the Fence Was Protecting
Service-minded leadership understands the purpose of a structure before changing who carries the risk.
Build the Buffer Before You Need It
Service-minded leadership builds slack before people need it.
Know the Boundary Before You Make the Promise
Resilient service starts by knowing what the system can actually carry.
Scale Only What People Can Still Trust
Before a decision scales, test what would make it fail the people it serves.
Turn the Map Into the Next Honest Step
Good leadership turns broad signals into local evidence and safer next actions.
Do Not Confuse the Map for the Decision
Good leadership connects public signals to local constraints before asking people to act.