Step 346. Leading a CTF Team — Becoming the Center of Gravity of a Winning Team

Level 4 — Professional | Difficulty ★★★★☆ | Estimated time: 3–5 hours (team diagnosis + strategy building + operations plan v2 consensus)

Prerequisites: the team charter v1 of Step 296 and the team-operations experience built across the competition series of Steps 324–328. If you don’t have a team yet, read this chapter as "the blueprint for when you build one."

What you need: the team charter v1 document, the member roster with each person’s competition logs, and a channel where you can convene a team meeting.
⚠️ All exercises in this chapter are for your own lab and legal platforms only. Applying them to unauthorized systems is a crime. Team training also happens only on legal CTF platforms and in your own lab.
Chapter type: today is a concept chapter — a day of handling people, not technology. And this is harder than technology.

A skilled player and a leader are different things. The person who solves problems fastest is not necessarily a good leader, and a good leader doesn’t have to be the best solver either. Rewrite the definition of a leader and it reads like this — not the person who solves well, but the person who makes the team solve well. The team’s total solve count is the leader’s metric, not your solve count.

You’ve already raised your team’s skeleton with team charter v1 (Step 296) and fought more than a dozen competitions together. What that experience tells you — overlapping strengths, empty fields, the fire that dies late in the season — you upgrade today into operations plan v2. Strategy, field allocation, motivation management. These three axes are the work of a center of gravity.

1. Learning Objectives

By the end of this chapter, you will be able to:

Diagnose each member’s strengths, weaknesses, growth desires, and available time to build a team status table
Build a season strategy (competitions to enter, target rank, training schedule)
Optimize overlapping strengths and empty fields through rotation and growth assignments
Turn burnout detection and motivation recovery into operating rules
Write team operations plan v2 and lead it to consensus in a team meeting

2. Background Knowledge — Today’s Tools and Concepts

Today’s Tools at a Glance

Category	Details
Language/environment	Team channel (Discord, etc.), shared documents, CTFtime — no new attack tools
Today’s commands	None — every deliverable is documents and consensus
Concepts needed	Team diagnosis, season strategy, field allocation (rotation, growth assignment), motivation management, center-of-gravity leadership
Today’s deliverable	Team status table + season strategy + field assignment table + motivation-management rules + team operations plan v2

2-1. A Leader’s Three Jobs — Strategy, Allocation, Motivation

Split the work of team leadership into three axes and it looks like this.

Axis	Question	Symptom when it fails
Strategy	Which competitions, with what goals	Entering competitions ad hoc whenever one pops up; a scattered season
Allocation	Who covers which field	Everything funnels to the strong; empty fields get discovered at every competition
Motivation	Does the fire stay lit all season	Unexplained absences late in the season; more "I’ve been busy lately"

The three axes hold each other up. Without strategy there’s no standard for allocation; forced allocation erodes motivation; dead motivation turns strategy into paper. That’s why the v2 plan carries all three axes in one document.

And let’s write down the leader’s real metric in advance — after finishing this chapter, what measures "how well did I lead" is not your contribution on the competition scoreboard, but whether the team is still gathering after the season ends. Keep that question in mind as you read the sections below.

2-2. The Rules of Diagnosis — Not Evaluation, but Data for Placement

One taboo when building the team status table — don’t rank people. The diagnosis’s purpose is not "who is good" but "which combination is strongest." The table has four columns.

Proven strengths: fields left as points scored in competition logs
Growth desires: fields the person says they want to learn next season
Available time: realistic weekly participation hours
Condition signals: recent participation rate, the tone of retrospectives — an early alarm for burnout

The "growth desires" column here is the difference between v1 and v2. If v1’s placement was "place people where they’re already good," v2 places people at the intersection of "where they’re good + where they want to learn." A placement without desire cools within three months; a placement with desire becomes points at competitions.

2-3. Two Techniques of Field Allocation — Rotation and Growth Assignment

The two problems you meet in allocation, and their techniques.

Overlapping strengths — if three people are good at web and nobody knows rev, you solve the overlap with rotation. A rule rotating the lead role each competition creates three things — fair opportunity, secured backup (a team that works even when one person is out), and the correction of each person’s weaknesses.

Empty fields — agree on "who will grow." Here a single sentence from the leader decides a field’s fate. "You do it" is a command, but "this season we’re picking an owner for rev — the condition is one lecture to the team after the competition" is a growth project. An empty-field assignment must always travel with authority and reward — problem-selection rights in that field, priority on training materials, and public recognition when points are scored.

2-4. Motivation Management — Devices That Keep the Fire Lit

Motivation is not a matter of praise — it’s a matter of design. Four devices that keep the fire from dying across a season.

Official celebration of small achievements — first blood, a personal best rank, a first solve in a new field. A celebration rule pinned in the channel multi-layers the competition’s goals — a team that has something to win today even without winning the contest does not collapse.
Fixed post-competition dinner/retrospective — held regardless of results. The retrospective after a loss matters more, which is why "do we hold it even when we lose?" is the device’s real test.
Burnout detection and rest encouragement — when you see participation dropping or a change in retrospective tone, speak first. The leader’s sentence is not "you’ve been skipping lately" but "you can sit this competition out." People return to teams that let them rest.
Managing the leader yourself — if the center of gravity collapses, the team scatters. Put the leader’s rest into the rules too.

2-5. Center-of-Gravity Leadership — Stand at the Center, Not in Front

The precise meaning of the phrase "center of gravity" — a presence that gathers the team into one point, not a presence that drags it from the front. During a competition, the leader’s actual actions are mostly things like these:

When a member is stuck for 2 hours, order a rotation (judgment)
When the mood sinks, bring an easy problem and make points (mood operations)
When information scatters across the channel, gather it into one document (information hub)
When conflict arises (problem assignment, solution direction), settle it by the standard (applying the charter)

None of these is "solving the hardest problem myself." The moment the leader immerses in the hardest problem, the team becomes a ship without a captain. The leader’s share is maximizing the whole team’s solve function, and that maximum sometimes appears as "a competition where I solved nothing." Enduring that is the leader’s training.

3. Follow Along

3-1. Diagnosing the Team — Into One Table

Collect self-reports across the four columns from every member and complete the table. Asking one-on-one for 15 minutes each is most accurate.

Team status table (screen example):
| Member | Proven strengths  | Growth desire | Hours/week | Condition signal         |
|------|------------------|-------------|-----------|----------------------|
| A    | web (top scorer) | cloud       | 10h       | good                 |
| B    | pwn, rev         | deeper rev  | 6h        | participation falling ← watch |
| C    | crypto, misc     | intro web   | 8h        | good                 |
| D    | forensics        | competition experience | 4h | newcomer, high motivation |

How to read it: from this table the leader sees three things. ① Empty fields — this team has only B as a rev lead, and his participation is wavering. ② Intersections — A’s "cloud desire" and C’s "intro web desire" are material for pair training. ③ Signals — B’s falling participation is something to approach before competition results.

3-2. Building the Season Strategy — Competitions, Goals, Training

Build the season calendar from CTFtime and domestic competition schedules.

Season strategy (screen example):
- Main competition: one target international competition (the one in Step 347) — goal: beat the team's best rank
- Support competitions: two domestic online events — goal: a test stage for new fields
- Training: weekly mock CTF (2 hours, rotated fields)
- Sharing: biweekly technique session — recent competition retrospective + empty-field study

The rule for goals — a rank goal is one step up from past data. "Win" is an aspiration; "last season 15th → this season top 10" is a plan. And goals must always pair with a growth goal — even if the rank misses, if "produced one rev lead" was achieved, the season was a success.

3-3. The Field Assignment Table — Applying Rotation and Growth Assignment

Turn 3-1’s table into assignments.

Season field assignments (screen example):
| Field  | Lead   | Backup | Rule                                    |
|-------|--------|------|-----------------------------------------|
| web   | A ↔ C rotation | — | alternate each competition; an intro-web curriculum supports C |
| pwn   | B      | —    | B's condition recovery comes first — reduced load        |
| rev   | B      | D (growth assignment) | D: 3 warmup-level rev solves within the quarter + 1 team lecture |
| crypto| C      | A    |                                         |
| misc  | everyone | —  |                                         |

How to read it: B’s row is this table’s core. Funneling everything to the strong is good for short-term results, but a team structure where pwn and rev both go empty if B collapses is a risk. Giving D the rev growth assignment is D’s growth — and also the team’s insurance.

3-4. Documenting the Motivation-Management Rules

Write 2-4’s devices down as operating rules.

Motivation-management rules (screen example):
1. Celebration: first blood / personal best / first solve in a new field gets an all-hands celebration in the channel (pinned message)
2. Retrospective: retrospective + dinner within 48 hours after every competition — regardless of results
3. Rest: when participation drops twice in a row, the leader reaches out 1:1 and names "a competition you may skip"
4. Leader rest: one designated competition per season runs under the deputy leader

You often see team rules missing item 4. A center of gravity needs a reserve center of gravity — that is the leader’s burnout prevention and, at the same time, the team’s leadership development.

3-5. Agreeing on Operations Plan v2 — The Craft of the Meeting

Bundle 3-1 through 3-4 into one document and hold a team meeting. Consensus has an order.

Diagnosis first — look at the status table together and get agreement on the facts. Conclusions reached after agreeing on facts generate little conflict.
Make the changes explicit — one list of what changes versus charter v1, and why. Every "why" is cited from 3-1’s data.
Take objections first — don’t ask "everyone agree?"; ask "what’s the one thing here that bothers you most?" Objections that don’t come out in the meeting come out mid-competition.
An effective date instead of signatures — the mark of consensus is writing the effective date in the document. And at the first quarterly retrospective, book v2’s first review. Consensus is not a one-time event but a process followed by review — with an effective date and a review date together, consensus becomes a living rule.

An example of the agreement document’s last line — "This plan gets revised at the season’s first retrospective. Not a perfect plan — a plan we fix as we use it."

The difference between a plan with this line and one without shows up a season later. The fix-as-you-use plan has become v2.1 by season’s end; the once-perfect plan sits discarded, out of step with reality. Same principle as Step 344’s playbook — a living document is a versioned document.

4. Missions & Exercises

Mission — Build Team Operations Plan v2 and Reach Consensus

Survey every member on the four columns (strengths, desires, available time, condition) and complete the status table
Build the season strategy (main competition, goals, training schedule) on the basis of past data
Build a field assignment table reflecting rotation and growth assignments
Document the motivation-management rules (celebration, retrospective, rest, leader rest)
Lead the team meeting to consensus, and leave the effective date and first revision date in the document

Exercises

Exercise 1. Explain the proposition "a good leader is not the person who solves well but the person who makes the team solve well," using the leader’s mid-competition action list (2-5) as grounds.

Exercise 2. The "growth desires" column of the team status table was called the difference between v1 placement ("where they’re good now") and v2 placement. Explain why a desire-less placement cools within three months.

Exercise 3. Explain why an empty-field assignment must travel with "authority and reward," through the difference between "you do it" and "the field’s owner."

Exercise 4. Explain why the rule of holding retrospectives "regardless of results" matters, and what this rule’s real test is.

5. Model Answers & Completion Criteria

Mission Model Answer

3-1 through 3-5 are the answer: status table → season strategy → assignment table → motivation rules → consensus document (effective date + revision date).

How to verify: ① Is each cell of the status table a member’s direct answer, not a guess? ② Does the target rank have grounds in past data? ③ Does the assignment table have at least one rotation and one growth assignment each? ④ Do the motivation rules include "the leader’s rest"? ⑤ Does the consensus document carry data citations for "why it’s changing" and a first revision date?

Exercise Answers

Answer 1. The leader’s mid-competition actions — ordering rotations, running the mood, serving as information hub, mediating conflict — all raise the team’s solve function; none produces the leader’s own solves. If the leader immerses in the hardest problem, all those actions stop and the team becomes a ship without a captain. If the team’s total solves exceed the leader’s personal solves, the leader’s optimal action is not solving problems but making problems get solved. The leader’s metric is not my contribution on the scoreboard but the team’s total score.

Answer 2. A desire-less placement is maintained by external motivation (the team’s need) alone, and external motivation is weak against friction — one bout of busyness, a losing streak, or a drift of interest, and the reason for the placement disappears. A placement with growth desire, by contrast, carries internal motivation (I want to learn this), so it returns on its own even when friction arrives. Three months is the felt period over which season fatigue accumulates and external motivation runs dry. That’s why v2 placement seeks the intersection of "where they’re good" and "where they want to learn" — and when there’s no intersection, it manufactures desire through pair training or curriculum support.

Answer 3. "You do it" transfers only costs — one person shoulders the learning cost and failure risk of an empty field, while ownership of the results stays ambiguous. Under these conditions the assigned person behaves defensively and, after a failure, comes to avoid the field itself. "The field’s owner" grants authority (problem-selection rights, material priority) and reward (recognition on scoring, a lecture stage) together — assets commensurate with the costs are given, so the assignment is redefined from burden to opportunity. The same assignment changes its outcome when its name changes.

Answer 4. A team that holds retrospectives only when it wins comes to see the retrospective as a celebration event, and when it loses — precisely when there is most to learn — the retrospective doesn’t happen. Then defeat’s data evaporates and the team loses again at the same spot. The "regardless of results" rule promotes the retrospective from an accessory of success to a basic operating procedure. That’s why this rule’s real test is "do we hold it even when we lose?", and the mood of that day’s retrospective — does analysis pass back and forth rather than blame? — is the team culture’s real form.

Completion Criteria Checklist

[ ] I completed the team status table (strengths, desires, available time, condition) from members’ direct answers
[ ] The season strategy has past-data-based goals and a training schedule
[ ] I applied rotation rules to overlapping strengths
[ ] I agreed on growth assignments with authority and reward for empty fields
[ ] I documented the motivation-management rules (celebration, retrospective, rest, leader rest)
[ ] I made "what changed and why" versus charter v1 explicit with data
[ ] I took objections first in the team meeting and reflected them
[ ] Mission: I wrote the effective date and first revision date into operations plan v2 and finished consensus

6. Common Pitfalls & Fixes

Wall 1. "I need to study too, and now leadership on top" — the burden is crushing

Symptom: since taking the leader role, your own training time has vanished.

Cause: the misunderstanding that leadership is the enemy of skill — it feels like a pure time-allocation problem.

Fix: leadership is not skill’s enemy — it’s multiplication. When the team gets stronger, what you learn grows too — teammates’ write-ups, sharing sessions, the stronger competitions a stronger team enters all become your learning assets. And leadership experience is a singular career asset — engineers are common, but "an engineer who built a team" is rare. Still, manage the reality of time — setting a weekday and hour cap on leader work is the condition of persistence.

Wall 2. Members end up in a power struggle over assignments

Symptom: "why is he the web lead?" — conflict around the rotation rule.

Cause: the assignment criteria aren’t in any document, so assignments read as the leader’s favoritism.

Fix: document the criteria first, then make individual assignments — in reverse order, every assignment becomes politics. If conflict has already arisen, use 3-5’s craft: return to the status table (the facts) and get agreement, and confirm that the rotation is "a rule belonging to no one." And from the next assignment onward, get rule consensus first, before the season starts.

Wall 3. When I — the strong one — don’t solve, the team’s score drops

Symptom: the team’s rank fell in the competition where you focused on the leader role, and self-blame arrives.

Cause: the leader role’s effect appears not in one competition but at season scale — optimized assignments, maintained motivation, growth in empty fields become points at the next competition.

Fix: change the evaluation unit — grade the leader not on this competition’s personal solves but on the whole season’s team total and the number of new solvers (members who produced a first solve in an empty field). Strategic judgment is still needed — at a decider like the target competition (Step 347), a hybrid operation where the leader also joins solving may be the right answer. Not the rule but the competition’s character decides.

Wall 4. A member vanished without a word

Symptom: a member who’d stopped attending retrospectives one day goes silent in the channel.

Cause: the burnout-detection device (2-4, item 3) didn’t fire — you saw the signals (falling participation, tone change) and still reached out late.

Fix: even now, contact them one-on-one — but wellbeing first, not a return request. "Come back to the team soon" closes the door; "how have you been — if you want to rest, rest" leaves it open. And fix the policy — add an automatic-outreach rule on two consecutive participation drops to the operations plan, made from this incident’s lesson. If you fail to learn from one person’s departure, a second departure comes.

Wall 5. Nobody objects in the meeting

Symptom: everyone nodded at "everyone agree?", then complaints erupt mid-competition.

Cause: questions asking for agreement make silence easy. Silence is often not consensus but avoidance.

Fix: change the question — have each person name "the one thing that bothers you most," going around. "One thing" being mandatory removes silence as an option. If nothing still comes out, the leader exposes one weakness of their own first — one sentence of "honestly, I’m not sure about this assignment either" often opens the floodgates of objection. Objections voiced in a meeting are assets; objections voiced mid-competition are accidents.

7. Summary

Today’s Concepts

Concept	One-line explanation
The leader’s three axes	Strategy (which competitions, what goals) · allocation (who covers which field) · motivation (keeping the fire lit)
Team status table	Four columns: strengths, desires, available time, condition — not evaluation but data for placement
Rotation	Fair distribution of overlapping strengths — the triple effect of opportunity, backup, weakness correction
Growth assignment	Assigning an empty field with authority and reward attached — "the owner," not "you do it"
Motivation-management devices	Celebration, retrospective, rest encouragement, leader rest — motivation is a design problem
Center of gravity	A presence that gathers the team into one point — binds from the center rather than pulling from the front

Today’s Deliverables & Procedures

Deliverable/procedure	What it does
Team status table	Data for placement — filled only with direct answers
Season strategy document	Main/support competitions, goals (past data +1 step), training schedule
Field assignment table	Three columns: lead, backup, rule — includes rotation and growth assignments
Motivation-management rules	Four articles: celebration, retrospective, rest, leader rest
Consensus procedure	Agree on diagnosis → state changes → objections first → effective and revision dates

The Core Instinct

Skill grows even alone, but a team scatters unless someone holds its center. What you made today is not a few pages of documents — it’s the structure by which a team endures a season. And this role’s reward arrives later than everyone else’s — next season, the message a teammate posts in the channel after taking their first flag in an empty field is the leader’s scoreboard.

Once every box is checked, Step 346 is complete.