26 · The Deliverer's Career Path: F1 to F5

Companion Templates

📋 Chapter Template (F1 to F5 anchors and the annual growth agreement, 3.7 and 3.8) · 🗂 Template Library

The Challenge. Three years in this work, then five, and what are you? Will you just be a firefighter who costs more every year?

What You Will Be Able to Do. Rate yourself with the F1 to F5 behavior anchors. Run an axis-by-axis self-assessment on the project you just closed out and find "the part you cannot carry." Write a one-page annual growth agreement that turns your next project into a step in career design.

The Weekend of Week 30, Two Ledgers

Friday of week 29, at the last retrospective at Anchor & Helm, you said nothing the whole time (Chapter 22). By week 30 you are already standing in a meeting room at Swiftway Logistics. Swiftway is another subsidiary of the Group, and the Group routed its ask to your team. The ask is "build an AI dispatch assistant," and what happened on that whiteboard is Chapter 23's story.

This weekend you spread out the Anchor & Helm project file and work a second ledger. The project's ledger is settled, -31%, L4, an impact memo Kevin Doyle wrote himself. This ledger is about you. In that project, which stretches did you run through cleanly, and which did you paper over with luck and overtime?

The honest list is not pretty.

Cleanly. The Field MVP (Chapter 0's 2-hour minimal prototype), the charter, co-building the eval, the three memos. You could run every one of these again tomorrow at any company.
On luck. Victor Reyes going from blocker to ally started with a pre-mortem that happened to draw him into asking for a meeting (Chapter 1). What if he had not come?
On overtime. The week the cost ran away (Chapter 16). The four fixes were clean, but the bill had gone to four times the estimate before anyone noticed, and that in itself is a failure to anticipate.
Taking the hit. The moment the survey team lead put his pen down (Chapter 20). You only learned to price visibility after the fact.

Then the colder question. If tomorrow's project is three times as complex, five business lines, three executives opposed to each other, data ten times worse, can you carry it?

You cannot. And that is exactly the good news. The part you cannot carry is your next level. This chapter gives you a ruler for measuring it.

Why This Is Hard: An Invisible Ladder

Growth in this role has a paradox. There is no ready-made job ladder for it. It does not fit the senior→staff line of code depth, because your code keeps getting zeroed out by AI and by handoffs. It does not fit the manager line either, because half of your "team" belongs to the business side. Ask "how does this role get promoted" and most organizations have no answer, and the Digital Center's job ladder has no row for it either.

People who cannot see the ladder move sideways. Five years, ten projects, case studies ready on demand, and all ten projects at the same difficulty, one sponsor, one business line, data bad in roughly the same way. That is experience 1×10, not 10×1. Project count is not experience. Complexity jumps are.

So the ladder has to be drawn first. The deliverer grows along one dimension only, the ceiling on the complexity of judgment, the ceiling on the ambiguity, the intensity of conflicting interests, and the organizational complexity you can handle. Anchor & Helm had exactly one Grant Whitmore from start to finish. Two Grant Whitmores pulling against each other is a problem of another order.

One distinction has to be set first. This book already has a ladder, the outcome ladder (L0 to L4, Chapter 1), and that one is the system's ladder. F1 to F5 in this chapter is the person's ladder. A system's outcome is counted in L. A person's capability is counted in F. Anchor & Helm climbed to L4, and what you graduated is F2. The two ladders do not convert into each other. An F4 on the wrong project can still watch the system die at L1. An F2 on the right project can take a system to L4, which is exactly what you just did.

Prior Art, and What AI Changed

Maister, growth in professional services is an apprenticeship. The three-layer structure in Managing the Professional Service Firm, finder (winning the work), minder (managing the relationship), grinder (doing the work), served Chapter 3 as a lens on time leverage (which layer a senior person's time should go to). Here it is a career path. A professional grows by moving up those three layers, and moving up runs on apprenticeship, which no classroom can teach. You follow a senior person on a real project and watch how he makes trade-offs where there is no right answer.

The Dreyfus model of skill acquisition, from rules to situations. The Dreyfus brothers' account of skill acquisition (novice → advanced beginner → competent → proficient → expert, five levels from beginner to expert) turns on one change in kind. A novice runs on rules, sees X and does Y. An expert runs on situations, stops retrieving rules, and simply "sees" what this situation is missing. This book gave you dozens of checklists and templates, and they are the novice's handrail. The book's goal is precisely that one day you stop checking them line by line. That is internalization, not forgetting.

What did the AI era change? AI is compressing, precisely, the value of technical execution inside F1 and F2 (the next section's table gives the levels). The part a coding agent can do devalues fastest, and the rate of devaluation is the rate at which models iterate. Two consequences.

First, the bottom step of the apprenticeship is disappearing. A newcomer used to trade grunt work for the right to be in the room. The grunt work now belongs to AI, and F1's ticket has changed from "can do the work" to "can review the work AI did."

Second, the whole growth curve tilts toward judgment and relationships. The earlier you move your assets out of execution and into judgment, the safer you are.

The other side of the same fact is that the deliverer is one of the few engineering roles in the AI era that gets more valuable the longer you do it. Chapter 6 said it. "Seeing that the Excel exists" is in no dataset. Scaled up to a career, it still holds. Field judgment is the hardest thing for a model to learn. It grows in specific rooms, the Thursday Linda Marsh stopped backing up the Excel, the weekly meeting where the survey team lead pushed back. Models cannot read those moments. You were there.

The Core Framework: F1 to F5, Five Levels × Five Axes

F1 to F5 is the deliverer's capability rating (F = field, meaning the level of a person's capability). It invents no new coordinate system. It reuses Chapter 3's five-axis capability self-assessment radar, engineering depth, AI engineering, business grasp, narrative, field judgment. The five axes here are capability axes. Chapter 25's intake rubric has five of its own, the five dimensions that score whether to take a project, and those are a different subject. Every level is given as behavior anchors, with adjectives set aside. "Senior" and "can stand on his own" cannot fix a level. "Has done this thing or has not" can. The full five-level × five-axis anchor table is in Template 3, and here is the main line.

Level	In One Sentence	Graduation Behavior Anchors
F1 Can Execute	Delivers inside a given charter	Work inside the boundary done to quality and on time; can spot exceptions and escalate them; can review what AI produced
F2 Can Deliver Alone	Goes from a vague ask to L3 or above alone	One sponsor, one business line, from "build an AI assistant" to a system in daily use and ready to hand off
F3 Can Handle a Complex Business Side	Delivers inside a conflicting interest structure	Several business lines, sponsors pulling against each other, strong opposition; a charter that opposing parties will both sign
F4 Can Lead and Productize	Amplifies judgment with multi-project leverage	Accountable for several projects at once; assets in the pattern library with you as owner; field insight carried across into product capability (the work of Chapters 23 and 24)
F5 Can Design the Practice	Designs the mechanisms that grow other people	The intake mechanism, the economic model, and the talent pipeline came from you; because of you the organization takes on fewer bad projects and produces more F3s (Chapter 25's organizational mechanisms are a work sample of F5)

Take one axis as a sample. The rating follows the lowest axis, and field judgment is the shortest plank in the self-assessment in the "At Anchor & Helm" section. Its five anchors are below, and the other four axes are in the same table.

Level	Behavior Anchor
F1	Spots anomalies and escalates the same day; can recite the red line list and holds it
F2	Ranks by irreversibility under time pressure; writes real causes of death in a pre-mortem; dares to write a readout (the conclusions report) that says "stop"
F3	Judgment still holds under conflicting interests. When two decision-makers pull against each other, handles it by written principle instead of picking a side in the moment
F4	Trade-offs at the portfolio level. Has judged, across several projects, which to save, which to kill, whom to send
F5	Has said no to an organization-level opportunity and offered a way out; the kill register and the retrospective discipline were built by you (Chapter 25)

Three rules for using it.

The rating follows the lowest axis, not the highest, the same as Chapter 3's rules for reading the chart. The five axes multiply, they do not add. Narrative at F4 and field judgment at F2 makes you F2.
The evidence for moving up is having carried it. Having taken part does not count. Serving as the F1 executor on an F3 project still grows F1 experience. The verbs in the anchors, signed, ruled, claimed, designed, must take you as the subject.
Each level absorbs the one before it. It does not replace it. An F4 still has to be able to deliver alone, only no longer by hand on everything. Whichever axis caves in, the person slides back to the level of that axis.

Three Paths Out, What Comes After the F Levels

Above F3 the road forks. Three common paths out, each with its own capability transfer map.

Internal incubation or a spinout. Take the proven pattern with you and start a new business or spin out a company. This role is one of the best founder trainings there is, because it covers the whole distance. What you did in these two years is spread across several chapters, and put together it is exactly a founder's capability list. Find the real need (the five questions and discovery, Chapters 7 and 6), deliver an outcome someone is willing to pay for (L3/L4, Chapter 1), win resources and renewed funding (the Trust Equation and the three memos, Chapters 5 and 19). Every core move of a startup's first two years you have already run for real. What you have to add is a shift in mindset. From serving one business line to selling one product, from "what does this business line want" to "which thousand companies want the same thing" (Chapter 24's three filters are the exercise).

Platform product owner. Take Chapter 24's field-to-product translator all the way and you are the platform product owner, distilling what the business lines have in common into an internal platform. You take the seat carrying assets nobody else has, the field radar, the n≥2 discipline, and real usage evidence in the decision trail data, and every business line's decision trail data is yours to read on one sheet. What you have to add is a switch in the scale of trade-offs. From one business line's outcome to a platform roadmap, learning to say no to the field the way you once said no to the platform for the field. You used to say no to the platform on behalf of the front-line business. Now you sit on the platform side and have to learn to say no to a business line on behalf of the platform.

Head of AI for the Group. Stay in the field and take F3 to F5 all the way. On one side, technical judgment the executives of every business line trust. On the other, the designer of the whole company's intake, eval, and delivery standards, and Chapter 25's mechanisms are the work sample for this seat. This path is the least glamorous and the scarcest. It demands fluency in both technology and organization, and both sides are short of people who have it.

Each of the three paths has an original outside the company, founder, product leader, field CTO. The capability transfer maps are the same, and only the market where you cash them in differs. All three share one hole card, the judgment banked by walking the whole distance. All three are ways of cashing in F-level assets, and none of them counts as escaping this role.

There is one more direction, not a path out but still a variable career design has to account for. Titles are drifting. Across the industry the boundary between field delivery roles and product engineering is thinning, and some companies have already merged the two hiring bars and reporting lines (from what two AI companies' deployment teams shared in 2026, paraphrased). Product engineers increasingly face users directly, and field delivery people go increasingly deep into product. Job names inside a company drift the same way. The day your title becomes product engineer or platform engineer, or the reverse, is not a change of career. Chapter 2 said it. The label drifts, the core does not move. The five axes travel with you, and the complexity you have carried is never zeroed out.

At Anchor & Helm: The F2 Graduation Exam and the Next Map

Axis by axis. Take the file you spread out over the weekend and run it through the five axes, accepting behavioral evidence only. The verdict comes in three grades. Solid, every anchor at that level has evidence with you as the subject, and the next level has none. Close to the next level, that level is solid and the next level's anchors have scattered evidence but not the full set, which does not change the rating and only tells you what the growth agreement should say. Barely, every anchor at that level has evidence, but some of it rests on luck or on after-the-fact repair, and in another field you might not carry it again. Put simply, solid is no holes, close to the next level is showing but not yet counted, and barely is just qualified but not certain to hold up somewhere else.

Axis	Behavioral Evidence	Verdict
Engineering depth	On a ten-year-old system under strict security constraints, took the merged view from design through to handing over lead-writer rights	F2 solid
AI engineering	Wrote the five-part eval spec (Chapter 11) alone, designed the monitoring surface alone, closed the loop on incidents and drift (Chapter 16)	F2 solid, close to F3
Business grasp	Dug out the fourteen-step real workflow; -31% converted into money and taken to the board	F2 solid
Narrative	The three-memo system; bad news volunteered within 24 hours; argued "the evidence says not yet" until it was accepted	F2 solid, close to F3
Field judgment	The red lines held, but the team lead's pushback was not anticipated, the cost blowout was handled by repair, and the Victor Reyes thread had a component of luck	F2 barely

The conclusion, F2 graduated, with a complete evidence chain. Going from two vague sentences to L4 on your own is the question paper of the F2 graduation exam.

Chapter 25's intake mechanism does not rewrite that conclusion. Having drafted an F5 exercise once is not rating evidence. A rating follows complexity carried again and again, and one draft is only another form of "having taken part."

The hardest line on the diploma is the week 26 impact memo, the one Kevin Doyle wrote himself. Your "able to step out of the daily" (Chapter 22) is not only a successful handoff. It is also the pass to the next rung of the F ladder. Sit on the last field as the irreplaceable person and you never free your hands for the next level of complexity.

The F3 gap. The weak planks on all five axes point at the same thing. Anchor & Helm's political environment was easy mode. One Grant Whitmore, an ally from day one. Even the heaviest no you said (week 28, when he proposed full automation, Chapter 25) was said to someone who trusted you. You have never handled two decision-makers pulling against each other. Who signs the charter, who hears the bad news first, whose North Star wins when the two conflict. On these questions you have not even given a wrong answer yet.

Swiftway is not a coincidence. During the handoff period there were two candidates for the next project, and the one you went to Owen Hartley to ask for was Swiftway Logistics, precisely because it is awkward. Dual Group and subsidiary sponsors, two decision-makers pulling against each other, exactly the complexity you have not carried. Whether its business looks like Anchor & Helm's is Chapter 23's question. Whether its politics look like Anchor & Helm's is this chapter's.

Inside a company, complexity jumps come from switching subsidiaries, switching divisions, and taking on more contested sponsor structures, from building a tool for one department to delivering one system between two competing divisions. And you have one thing people outside do not. Every ask queued in the company sits on the PMO register and the intake list (Chapter 25), so you can see which kinds of sponsor structure next year holds, and all you have to do is ask. Project selection is career design. Projects that come to you keep you moving sideways. Projects you choose are the ones that move you up.

The annual growth agreement. Land this self-assessment on one page. What complexity you will carry next year, which piece is missing, which project fills it (template at Template 3.8). Your worked example is below.

What you carried this year, one sponsor, one business line, from a vague ask to L4 (graduating F2). What you will carry next year, deliver an L3 or above once under the conflicting interests of dual sponsors (F3's first question). The gap, the F3 anchors on field judgment and narrative, a charter co-signed by opposing parties, and information discipline under conflict (rules of the "who hears the bad news first" kind). Which project fills it, Swiftway Logistics (a dual Group × subsidiary structure). Six-month checkpoint, draw the dual-headed stakeholder map with both sides agreeing to it; the first time instructions from the two sides conflict, handle it by the principle written down in advance rather than picking a side in the moment.

This page is worth something not on the day you fill it in but at the reconciliation six months later. Like a pre-mortem, it turns growth from "something that happens to you" into "something you arranged to happen."

Failure Modes

1. Moving sideways. Ten projects in five years, all at the same difficulty, a resume that keeps getting longer and a level that will not move. Project assignment is usually not yours to control, and the assignment logic is "give it to whoever has done something like it." The organization wants certainty and you are attached to the comfort zone, and the two conspire to pin you at one level. Moving sideways is better hidden inside a company, because one company's projects naturally converge in difficulty. Five years on you may be the person in the company who understands one business line's AI best, and nothing more. And the F ladder is invisible, so repetition sets off no alarm. The fix is this chapter. Make the ladder explicit, negotiate project selection as career design, and go ask for the awkward business lines. The test, look back at your last three projects. If the sponsor structure and the hard problems are all of one kind, you are moving sideways.

2. The permanent firefighter. Wherever something breaks, there you are, the business side asks for you by name, and you are quietly proud of it. This is a two-way addiction. The organization needs you to fight fires (you are its cheapest reliability), and you are addicted to being needed (firefighting feedback is a strong hit on an hourly cycle, Chapter 3's firefighter mode trap inside the operator identity, recurring at career scale). Every fire postpones your F3. Firefighting spends nothing but the judgment you already hold, and it grows none. And "being needed" is the exact opposite of "able to step out of the daily," so the pass upward is one you burn with your own hands. The test, think back to the judgment you used in your last firefight. Was any of it grown in that field? If it was all judgment you already had, you are being consumed.

3. Growing technically without growing in judgment. Every new model and framework tried first, the left half of the radar (engineering depth, AI engineering) rising year after year, and the right half (business grasp, narrative, field judgment) not moving at all. Technology has courses, documentation, and instant feedback. Judgment has no textbook. It grows only out of real projects with retrospectives, and a retrospective you skip is a saving you keep forever. This leg is the one AI is eating, precisely. You are racing a coding agent's price curve, and it does not sleep. The test, open your last archived radar. Did the behavioral evidence on the three axes in the right half change? Scores up with the evidence unchanged means nothing went up.

4. Leaving the field too early. Two years in, one full cycle done, and you move into investing, consulting, or evangelism, more and more stage and less and less field. The title premium on F2 is at a high right now ("has shipped AI in production" sells well in the market), and the temptation to cash out is real. But judgment has not taken root. One cycle is only enough to run the book's frameworks through once, not enough to know what to do when a framework fails. The test, all the stories you tell are other people's, or you have been telling the same story of your own for two years.

Vendor View

On the vendor side, complexity jumps come from changing clients. The next project is set by the sales pipeline, and the difficulty is not yours to pick. The three paths out come in their original form, founder, product leader, field CTO. The capability transfer maps are the same, and only the market where you cash them in sits outside the company.

Next Monday

Run an F-level self-assessment on the project you just closed out (or the one in hand). Find behavioral evidence axis by axis, and rate by the lowest axis. Write down the "papered over with luck and overtime" list. That is the syllabus for your next level.
Write a one-page annual growth agreement with Template 3.8. The "six-month checkpoint" has to be filled with verifiable behavior, not an adjective.
Look at the next project waiting for you. Does it hold complexity you have not carried? If not, go through the asks queued on the PMO register, pick the one with the most awkward sponsor structure, and go talk to Owen Hartley this week with your growth agreement in hand.
Archive today's five-axis radar (Template 3). What you compare a year from now is not the scores. It is whether the behavioral evidence behind each axis changed.

Want an agent to get you started? In the repo you set up following Start Here, paste this to your coding agent:

In the repo/ directory of the the-last-mile repository, help me with the Chapter 26 Next Monday actions. First run python3 templates/f-levels/radar-to-flevel.py
with the built-in sample to show how historical radars map to F levels, then copy questionnaire.md into the working directory I name. The behavioral evidence for the five axes
I will dictate axis by axis, and you only record it. The rating follows the lowest axis, and the level is mine to set, not yours to compute. Build the skeleton of the annual growth
agreement from Template 3.8, and if I write an adjective in the "six-month checkpoint" hand it back and make me replace it with verifiable behavior. Archive today's radar CSV by date,
side by side with my Chapter 3 one. If any command errors, stop and show me the output.

Chapter Kit

Judgment frameworks. The F1 to F5 capability rating (five levels × five axes of behavior anchors; kept strictly apart from the outcome ladder, systems counted in L, people counted in F); the capability transfer maps for the three paths out (internal incubation or a spinout / platform product owner / head of AI for the Group); the annual growth agreement (what you carried this year → what complexity you will carry next year → the gap → which project fills it → six-month checkpoint)
Templates. Template 3, Capability Self-Assessment and F1–F5 Rating, the F-level half (3.7 and 3.8), behavior anchor table plus the annual growth agreement template
Key judgments
"Project count is not experience. Complexity jumps are."
"Field judgment is the hardest thing for a model to learn. It is in no dataset."
"Project selection is career design."
"A system's outcome is counted in L. A person's capability is counted in F."

From That Monday Morning to This One

The Monday morning of Chapter 0, nine o'clock, fifteen minutes, and all the information in your hands was two sentences, "we want an AI assistant" and "I want to see something in three months."

Thirty weeks later, take stock of what you carry away. Not the code, which stays in Anchor & Helm's repo, and even the lead-writer rights are not yours. The -31% counts for only a small share. What you really carry away is a body of judgment built by walking the whole distance.

When to build a 2-hour MVP instead of a six-week study.
Which signal means it is time to switch identity.
When data can be trusted.
How to co-build an eval.
How to deliver bad news.
When to say no.
How to step out of the daily.

And a map. You know where you stand between F2 and F3, you know what the next level's questions look like, and you know why the project in hand is this one.

Next Monday morning, in Swiftway's meeting room, someone will say something vague to you again. This time you will not be nervous, and you should not be casual either. Everything Anchor & Helm taught you will be examined again there, plus one new question you have never worked.

The road this book can walk with you ends here. The rest of the road, like judgment, is in no dataset. It is in your next field.