Each Field Note documents a real organizational problem, the reasoning behind how it was approached, and the principle that outlasted it — evidence of how I think, not a project report.
The work that follows isn't a portfolio in the traditional sense.
These Field Notes document how I approach organizational problems through systems thinking, operational design, and strategic partnership. They don't attempt to capture every decision or reveal every implementation detail. Instead, they focus on the reasoning behind the work, the principles that shaped it, and the organizational outcomes that followed.
Where relevant, each Field Note is paired with the operating system, planning framework, or decision tool it produced — not as the point, but as proof the thinking held up in practice.
Together, they trace one instinct: the reasoning was always there. These just make it visible enough for someone else to use.
The quality of a design hire is determined long before the first candidate enters the pipeline — it's determined by the partnership that shapes every decision afterward.
A hiring plan's job isn't to move faster than uncertainty. It's to design around the constraints you already know about before they become emergencies.
The flagship piece — held for a dedicated reconstruction from the complete body of primary source material.
Rubrics don't create alignment. Shared reference points do — because a rubric is still just words until the panel has agreed on what those words look like in an actual person.