The method
Name what matters. Then go move it.
Goal Boss began as a book about finishing what you start. The method inside it fits on this page, runs on paper, and takes about an hour a month. It rests on three pillars, adds five principles, and ends with a ten-minute drill for getting unstuck.
Where it starts
Two questions, asked before anything else
Every part of the method sits on top of these. Ask them at the start of a project, a meeting, or an email, and most of the confusion you were about to create never happens.
Question one
What is the goal?
Without the goal, it is hard to know what to do. Say it out loud and the room stops guessing. A meeting that opens with the goal ends sooner. An email that opens with the goal gets a useful reply.
Question two
Who is the leader?
There is always more than one way to do something, so somebody has to make the call when the team splits. When nobody is in charge, everybody is in charge, and the work stalls in the middle.
The system
Three pillars, run in a loop
Success is a process, not an event. In business it comes down to fifteen or twenty things you measure, set goals against, and refuse to let problems stall. That is the whole system.
Key Metrics
The things in your business that actually decide whether you win. Most teams can feel them and cannot name them, so the method gives you a way to get them on paper in twenty minutes.
Goals
Once you know your Key Metrics, you set goals built to move them. Raise revenue, cut cost, close more deals. A goal with no metric behind it is just a nice idea with a deadline.
Team Problem Solving
Something will get in the way, because it always does. This is a timed ten-minute drill that turns a problem into action steps with dates on them, so you stop relitigating it every month.
Pillar one
Find your Key Metrics with two lists
The idea of a Key Metric gives nobody trouble. The things that matter most are, by definition, key. Naming them is where people stall, so the method skips the workshop and uses an exercise that takes about twenty minutes.
Write the ten things you are most proud of. Then write the ten things you are most worried about. Your Key Metrics are sitting in those two lists, and you already knew every one of them. Run the exercise with your team and you get the Key Metrics for the whole organization instead of one person's view of it.
Be honest, and do not flinch. A worry list that leaves off the thing you actually lie awake about produces a metric set that measures the comfortable parts of your business.
10
Things you are proud of
Maybe it is the retention rate nobody else in your category hits, the product line that carries the year, or a crew that never quits. Write them down without hedging.
10
Things you are worried about
Cash in ninety days, the one client who is a third of revenue, the hire you keep not making. These tend to name themselves faster than the first list.
Pillar two
Six goals, and only six
With the metrics named, you set goals to move them. The method asks for six, in three pairs, and the number is deliberate. A list of twenty goals is a list of zero goals.
Write them down. A goal that lives somewhere other than your head is the one you actually finish, which is dull advice and works anyway.
The split matters. Your business goals pay the organization. Your professional development goals pay you, and you take them with you if you ever leave.
-
2
Short-term business goals
Finished in the next thirty to forty-five days. Close enough that you cannot quietly postpone them.
-
2
Long-term business goals
Finished inside twelve months. Big enough to change a Key Metric rather than nudge it.
-
2
Professional development goals
About you, not the company. The leadership skill you know is capping what you can take on.
Pillar three
Team Problem Solving takes ten minutes
The structure comes from how NASA teams work a problem. One person brings it, the team attacks it, and the clock runs the meeting instead of the loudest voice. It starts with a question that begins "how to."
1min
Background and facts
The person with the problem gets sixty seconds to say what is wrong and how it is hurting the team. When the minute is up, the minute is up.
2min
Questions and answers
The team asks. Questions stay short because time is short, and answers stay shorter. Two minutes buys the team enough to work with.
5min
Suggested action steps
Everyone tells the client what to do. The client does not speak at all, and writes down every suggestion without judging any of them.
2min
Stop and jot
The client picks the steps worth taking and writes a date next to each one. Those dated steps become goals, in front of the team.
The five silent minutes do the heavy lifting. A client who is allowed to argue spends the whole window defending the situation, and the team stops offering. Staying quiet is the discipline that makes the other nine minutes work. Run three of these in a meeting and you will clear more in half an hour than most teams clear in a quarter.
The principles
Five principles underneath all of it
The pillars are the machinery. These are the values the machinery assumes, and three of them are also the three things most likely to end a career.
Teamwork
Individuals go fast, teams go far. In rowing, your personal goal is to make sure your boat is the best boat, rather than to be the best rower in it.
Hard work
Take the smart people, and we will take the hard workers. Eight times out of ten the hard workers win, because grit shows up when things stop coming easily.
Communication
Getting someone to actually understand your thoughts is a skill, not a gift. Nobody is born with it, and nobody has ever finished learning it.
Delegation
Ask whether anyone else could do the task you are about to start. If somebody could, hand it over. Only do what only you can do.
Time management
Time is the one thing you cannot get more of, yours or anyone else's. Nobody trusts a thief, and a meeting that runs long steals from everyone in it.
Where the method runs
Two things make a meeting a meeting
Without both of these you have a get-together. Everybody names the first one immediately, and almost nobody has the second one written down.
Must one
A written, shared agenda
It sets the topics and the times. Everyone knows what you will cover, what the meeting is for, when it starts, and, best of all, when it ends. Certainty is worth more than most people give it credit for.
Must two
Ground rules
A conference room is a purpose-built environment where careers stall, customers are lost, and trust erodes. Every other room like that has rules posted on the wall. Goal Boss clients post these.
- ✓ConfidentialityWhat is said here is not repeated outside. That is what makes it safe to say the real thing.
- ✓TeamworkWe work as a team, and a promise made to the team gets kept.
- ✓Everyone participatesEven the quiet ones speak, and they are usually the best informed people in the room.
- ✓No sidebarsTwo people running their own meeting inside the meeting removes both of them from it.
- ✓Airplane modeIf you have time to clear email during the meeting, the meeting was not worth holding.
- ✓Candid, timely feedbackBe ready to give it and to take it. Silence to avoid discomfort costs the team more.
- ✓Manage time ruthlesslyStart on time, end on time. Do not take hostages.
The method under pressure
Where this meets AI
You can run every bit of the method on paper, and plenty of people do. What paper will not do is chase the action steps after the meeting ends, which is where most of this quietly falls apart.
The method did not change when AI arrived. What changed is the load on it. Decisions arrive faster than the cadence was built for, the ground moves inside a single quarter, and the manager in the middle is asked to explain a change they cannot honestly underwrite.
Judgment Day is this method under that load: what AI breaks first, how to organize when the ground shifts every ninety days, and what to say when you cannot promise anyone their job. The readiness assessment on this site is the one from its tenth chapter, built to be answered rather than filled in.
For the people side of a rollout, start with AI transformation, then AI change management, on what managers say and do, AI adoption strategy, on why usage stalls after launch, and AI training for employees.
None of it is a prerequisite. An engagement starts from whatever a team already runs, and the vocabulary is optional. Adoption is a result, never a toll on the way in.
Questions
Common questions about the method
What is the Goal Boss method?
The method rests on three pillars. Key Metrics are the fifteen or twenty things that decide whether your business wins. Goals are what you set to move those metrics, each one carrying a date. Team Problem Solving is a ten-minute timed sequence for clearing whatever is blocking a goal. You run the three in a loop, and the loop is the method.
How do I find my Key Metrics?
Write the ten things you are most proud of, then the ten things you are most worried about. Your Key Metrics are sitting in those two lists. Do the exercise with your team rather than alone and you get the Key Metrics for the whole organization.
How long does Team Problem Solving take?
It runs ten minutes, split four ways. The client gets one minute of background and facts from the person with the problem, two minutes of questions and answers, five minutes in which the team suggests action steps and the client stays silent, and two minutes for the client to choose steps and put a date on each. Three rounds fit comfortably in a half-hour meeting.
Do I have to buy the book to use the method?
No. The method is on this page in full and you can run it on paper in your next meeting. The book goes deeper on leadership, communication, planning and coaching, and it is where all of this came from.
Pick the two lists. Start there.
Twenty minutes with a pen gets you your Key Metrics. Everything else in the method hangs off that one exercise.
The diagnostic takes four minutes. No account, and nothing you enter is stored.
