Tools & templates

Game Diagnosis Worksheet

A 15-prompt worksheet for freelance problems that keep coming back: map the players and incentives, name the pressure point, and pick one structural fix.

checklistUpdated Nov 03, 2026

When to use this

  • The same freelance problem keeps returning under different names.
  • You feel reactive and want to understand the structure before acting.
  • A client situation feels messy and you want the cleanest next move.

Preview

Progress

0 / 15 complete

See the game before you play the move.

Define the problem

Map the players

Find the pressure point

Choose the next move

How to use this worksheet

This game diagnosis worksheet helps you work out why a freelance problem keeps coming back, and which small rule would stop it. Fifteen short prompts take you from the visible symptom, through who wants what, to one structural fix you can test on the next project.

It is for the moment before the emotional reaction takes over. The goal is not to theorize forever. It is to name the structure clearly enough that the next move becomes obvious.

Use Copy as Markdown to put the prompts in your own notes, then write your answers under each prompt. The on-page checkboxes track which prompts you have completed, and the copy marks those prompts as checked; neither captures your written answers.

  1. Name the visible symptom in one sentence.
  2. Map the players and what each side wants.
  3. Identify what is hidden, rewarded, or repeating.
  4. Choose the smallest structural fix and make it a default if it works.

When to run it

Run the worksheet when a freelance problem feels bigger than the message in front of you. Good triggers include repeated scope creep, a lead that keeps demanding free strategy, a client delaying payment, a project that always needs one more revision, or a workload that keeps becoming “temporarily” unsustainable.

The worksheet turns the problem from “What should I say?” into “What is this situation rewarding?” That distinction matters. A better reply may solve today. A better rule solves the repeat pattern.

The seven games, in plain terms

Prompt 8 asks you to name the main game. These are the seven that cover most freelance problems, with the usual symptom and the kind of fix that tends to work.

  • Signal: good clients cannot tell you apart from cheaper options. Fix with proof that is costly to fake: specific case notes, a clear offer, a paid diagnostic.
  • Screening: you keep taking leads that turn out badly. Fix with questions asked before scope, using the client screening checklist.
  • Bargaining: every price conversation ends in a discount. Fix with a floor, an option set, and trades instead of concessions.
  • Contract: disagreements about what was included. Fix with written scope, acceptance criteria, and a change-request rule.
  • Payment: invoices drift past due with no consequence. Fix with deposits, short terms, a reminder sequence, and a pause rule.
  • Repeated trust: a long-term client slowly stops respecting boundaries because each exception became the new normal. Fix by resetting one default in writing.
  • Optionality: you accept bad terms because you have no alternative. Fix by building pipeline and reducing dependence on one client.

How to interpret the answers

  • If the same symptom repeats, look upstream: scope, payment terms, discovery, or expectations.
  • If one side has hidden information, add a question, milestone, or paid diagnostic.
  • If bad behavior is cheap, add cost: a pause rule, change request, fee, or clean no.
  • If good behavior is hard, reduce friction: templates, defaults, deadlines, or single owners.

Example diagnosis

Symptom: client keeps asking for “tiny” extra changes.

Current reward: extras are free and fast if they ask casually.

Structural fix: define review windows and route every new request through a written change request.

Worked example: the client who always pays late

A hypothetical full run of the worksheet, written the way you would write it in your own notes: one line per prompt.

Define the problem. Symptom: a monthly retainer client has paid 10 to 20 days late for four months. Repeat: every invoice, not just one. Cost: I float about two weeks of expenses and spend an hour a month chasing.

Map the players. Me, my contact (a marketing lead), and their accounts payable team. The contact wants the work to continue; accounts payable wants to batch payments; I want predictable cash. Accounts payable may not know my terms at all, and I do not know their payment run dates.

Find the pressure point. Main game: payment. Rewarded: paying late costs them nothing. Cheap but harmful: I keep working while invoices are overdue. Easier good outcome: invoice timed to their payment run, sent to the right address, with terms they have accepted.

Choose the next move. Smallest fix: ask accounts payable for their payment run dates and invoice requirements, then move my invoice date to match. Tool: the late payment checklist. Next written action: an email to my contact today. Default if it works: confirm payment runs and invoice requirements with every new client at onboarding.

Notice that the fix is not a firmer reminder. The structure showed that the late payments came from an invoice that did not fit the client's process, and that continuing to work cost the client nothing. If the timing fix does not work, the late payment checklist covers the escalation and work-pause steps.

Common mistakes

  • Diagnosing the person instead of the setup. “The client is difficult” is not a structure you can change. “Extra requests cost nothing” is.
  • Choosing a fix that needs the other side to change first. The smallest fix should be something you can do this week.
  • Skipping the last prompt. If a fix works and you never make it a default, the problem returns with the next client.

Many repeat problems trace back to unpaid extras that became normal. The guide to stopping free work shows how to reset that default without a confrontation, and the scope change checklist turns the change-request fix from the example above into a routine.

Where to go next

If you are not sure which area of the business is under the most strain, run the freelance business health check first, then use this worksheet on its weakest area. The ideas behind the prompts are explained in freelancing is game theory. For a bargaining problem, prepare the next conversation with the negotiation prep and concession planner; for an optionality problem, the client concentration scorecard shows how exposed you are.

Use with

FAQ

How detailed should I get?

Only detailed enough to change your next move. If the worksheet becomes procrastination, stop and act.

Can I use this for workload problems too?

Yes. Burnout and overload get clearer when you map incentives, commitments, and concentration.

How long should one diagnosis take?

Usually 15 to 30 minutes. Write one or two lines per prompt. If you cannot answer a prompt, mark it as a question to find out rather than guessing at length.

What if more than one game seems to apply?

Pick the earliest one in the project timeline. A payment problem that started with a vague scope is usually a contract game first, and fixing the contract default prevents the payment problem on the next project.

Do I need to know game theory to use it?

No. The prompts only ask what each side wants, what they know, and what behavior is cheap or rewarded. The game names are labels that point you to the right fix, not theory you need to study first.

How to customize

  1. Add your own common failure modes if you keep seeing the same stress pattern.
  2. Keep answers short enough that the worksheet still leads to action.

Common pitfalls

  • Using the worksheet as procrastination instead of diagnosis.
  • Solving the loudest symptom instead of the earliest structural break.

Related Codex pages

Comments

Sign in to comment.

Loading comments…