--- title: "Manage the Team: Goals, Trust and Delivery" author: "Harry" published: 2026-10-31T04:50:50.850Z updated: 2026-10-31T05:08:37.645Z category: "Career & Teams" tags: [] canonical: "https://fxblog.dev/posts/how-to-set-team-goals-as-a-lead" --- # Manage the Team: Goals, Trust and Delivery ## Key takeaways - Three objectives with two or three measurable results each fit on one page, and everyone can remember them. - Every result has one owner who decides how to reach it; the lead decides what and why. - Delegating means agreeing the outcome and the check-in, then staying out of the how. - A weekly update upward says done, next, risks and asks, in five lines. - Report a red result early with a plan attached; bad news delivered late is what destroys trust upward. > **TL;DR** A quarter plan with eleven goals is one nobody remembers, and a red result your boss discovers in week 12 costs more trust than the miss itself. How to set team goals as a new lead: a few measurable results on one page, one owner each, a five-line update every Friday, and red reported the week it turns red, with a cause and a plan. > > **Do this:** This Friday, send your manager a five-line update: done, next, risk, ask, and the colour of each goal. Part 3, **One-to-Ones That Matter, and Handling Conflict**, ended with a calm crew and a blank line: next quarter's plan, due to the Admiral on Friday, with nothing where the checkout crew's goals should be. Pip filled it in that night. Her first draft had eleven goals. Ollie read it over breakfast. "If the Admiral remembers one line of this, which line?" **Dev Voyage: Uncharted Waters, in five parts:** 1. **From Best Engineer to First-Time Lead** 2. **Hire and Grow Your Crew** 3. **One-to-Ones That Matter, and Handling Conflict** 4. **Manage the Team: Goals, Trust and Delivery** (you are here) 5. **Build the Ship You Want to Sail On: Culture and Giving Back** ## Eleven goals is no goals Pip couldn't answer. Then: "Checkout should fail less." "That's your first objective," said Ollie. "What number tells us it's true?" Google's re:Work guide to OKRs, objectives and key results, describes the shape: the objective says where you want to go, and each key result is a measurable step that shows whether you got there. Pip cut eleven goals to three objectives. ```text Objective 1: Checkout customers can trust KR 1.1 Failed payments retried safely; zero double charges owner: Brock KR 1.2 Checkout error rate below 0.5% of sessions (now 1.2%) owner: Pip KR 1.3 Every checkout incident has a blameless note in 2 days owner: Bun Objective 2: A crew that ships every week KR 2.1 No pull request waits more than one business day owner: Pip KR 2.2 Quill owns the discount service end to end owner: Quill Objective 3: Fewer surprises for the business KR 3.1 Release dates shared two weeks ahead, with risks owner: Ollie ``` The numbers are Pip's story, not a benchmark. Yours come from your own dashboards. The test is whether someone who wasn't in the room could check each line. ## One name per result Every key result has one owner. Not "the team", not two people. The owner decides how to get there, and raises a hand when it's stuck. Pip kept two results and gave the rest away, including KR 2.2, a growth goal for Quill as much as a delivery one. | The lead decides | The owner decides | | --------------------------- | ------------------------------- | | What the result is, and why | How to reach it | | When to check in | What to try first, what to drop | | The limits: budget, risk | Who to pair with | Her weekly check-in question changed from "how are you doing it?" to "what's blocked, and what do you need from me?" ## Five lines every Friday The Admiral didn't want a meeting. He wanted to know, each Friday, whether checkout was on course. Pip sent the same five lines every week. ```text Done: Retry logic shipped (KR 1.1). Zero double charges in 7 days. Next: Error-rate fixes for the address form (KR 1.2). Risk: KR 1.2 is RED. Error rate 1.1%, target 0.5%. Cause: a third-party address API times out at peak. Plan: cache + fallback, 2 weeks. Ask: Approval to spend 2 days of Brock's time on the fallback. Green: KR 1.1, 2.1, 2.2 Amber: KR 3.1 Red: KR 1.2 ``` ![A weekly check on each key result: green stays with its owner, amber gets help, red goes to the Admiral that week with a plan; hiding red costs trust](https://fxblog.dev/media/01a1904b-ab30-742f-b294-974cdb5d0575/1600) _Red early, with a plan_ ## Red in week 4 That third line nearly didn't get written. Pip's instinct was to wait a week and hope the number improved. > **Note** > > **Pip:** If I report red, he'll think I can't lead. > **Kit:** Red in week 4 with a plan says you can. Red he finds in week 12 says you hid it. On Friday the Admiral read it twice. "Red, with a cause and a plan. Approved!" A red result is reported by the lead and never blamed on its owner. KR 1.2 was Pip's, but the rule would be the same if it were Quill's: the update says what is red and why, not who failed. > **Warning** > > Some red is expected. re:Work's guide treats about 60–70% as the sweet spot for stretch goals, so a team that always hits 100% aimed too low. Agree with your manager which results are commitments and which are stretches. ## Try it This quarter: 1. Cut your team's goals until everyone can say them without looking. 2. Give every key result one owner and a number someone else can check. 3. Send a five-line update every Friday: done, next, risk, ask, colours. 4. Report red the week it turns red, with a cause and a plan. The quarter ended with two results green, one amber, and the red one fixed in week eight. Quill owned the discount service and had started answering newcomers' questions himself. Pip looked at her crew and wondered what she was building beyond the work, and what would still be there if she moved on tomorrow. Part 5, **Build the Ship You Want to Sail On: Culture and Giving Back**, is her answer, and the end of the voyage. ## Read this with your AI ```text Read the post "Manage the Team: Goals, Trust and Delivery". 1. I'll paste my team's draft goals. Cut them to three objectives with measurable key results. 2. Suggest one owner for each key result, given these people and their growth goals: [list] 3. Turn this week's notes into the five-line update: done, next, risk, ask, colours. ``` > **Success** > > You can set a quarter plan your team remembers, delegate it, and report up honestly. Next: **Build the Ship You Want to Sail On: Culture and Giving Back**. ## FAQ ### How many goals should a team have per quarter? Few enough that everyone can name them without looking: often three objectives, each with two or three measurable results. If everything is a goal, nothing is. ### How do I check progress without micromanaging? Agree the outcome, the owner and a weekly check-in up front. In between, ask what is blocked and what help is needed, not how the work is being done.