Written by Tool 1 of 5: The First Minute — Context, Intent, Key Message
You’ve got an idea. A game concept, a portfolio piece, a job you want. You sit down in front of the person who can say yes — a studio lead, a potential collaborator, a hiring manager — and they ask: “So, tell me what you’re working on.”
What comes out next either opens a door or closes it.
Most people freeze, ramble, or bury the important stuff under a mountain of backstory. Not because they’re not talented. Because nobody ever taught them how to talk about their work in a way that makes the other person want to keep listening.
That’s what this post is about.
Why This Matters More Than You Think
Here’s something the game industry won’t always say out loud: your idea only gets a chance if you can communicate it clearly in under a minute.
Studios receive hundreds of pitches. Hiring managers spend an average of six seconds on a resume before deciding whether to read further. A potential collaborator on Discord will decide in the first two messages whether you’re worth their time.
This isn’t about being slick or salesy. It’s about respecting the other person’s time and being clear about what you need. And it’s a skill — which means it can be learned, practised, and improved.
The framework that changed how I think about this came from communications specialist Chris Fenning’s book The First Minute. It sounds deceptively simple. That’s the point.
The Framework: Two Structures, Two Directions
There are two conversations you need to get good at as a game developer, a career-starter, or someone transitioning into a new industry.
When you’re pitching outward — presenting your concept, asking for feedback, seeking approval — use:
Context → Intent → Key Message
- Context: The minimum the other person needs to understand the situation right now. One sentence. No history, no backstory, no “so basically what happened was…”
- Intent: Tell them exactly what you need from this conversation. A decision. Feedback. An introduction. Be specific.
- Key Message: The one thing they must walk away knowing or doing.
Here’s what it sounds like in practice:
“I’m developing a mobile puzzle game for commuters aged 18–35. I’d love your feedback on the core loop before I start prototyping. The main question I need answered is whether the mechanic is intuitive enough to test with real users.”
That’s it. Thirty seconds. Clear, confident, and gives the other person exactly enough to engage.
When you’re receiving a brief — taking on a project, clarifying a client’s needs, scoping work with a team — use:
Goal → Problem → Solution
- Goal: What does the person actually want to achieve?
- Problem: What’s standing in the way right now?
- Solution: What are you proposing, and why does it directly address the problem?
In a game development context, this is how you respond to a client or studio brief without wasting weeks building the wrong thing:
“Your goal is a casual game that builds daily habits in your users. The problem is that your current onboarding takes four minutes — research shows most mobile players abandon a game in 90 seconds if they haven’t reached the core mechanic. My solution is to redesign the entry sequence so players are playing within 60 seconds.”
That’s not a student answering a brief. That’s a professional solving a problem.
Why This Is Especially Important for School Leavers and Career Changers
If you’re coming from a gaming background into the professional world, or moving from a different industry into game development, you’re likely carrying one of two habits that will work against you:
Habit one: Over-explaining. You know your work deeply, so you explain everything — the inspiration, the process, the challenges, the iterations — before you get to the point. The other person has stopped listening by then.
Habit two: Under-claiming. You downplay what you’ve built because it’s “just a student project” or “only a hobby.” You bury the lede so far down that the other person never sees the value in what you’ve done.
The First Minute framework fixes both. It forces you to lead with what matters, state what you need, and trust that the detail can follow if the other person wants it.
Practical Tips: How to Build This Skill Right Now
1. Write your Context sentence today.
Open a blank document and write: “I am building [X] for [Y audience] because [one-line reason].” That’s your Context. Keep it to one sentence. If it’s longer, cut it.
2. Practise with a timer.
Set 60 seconds on your phone. Deliver your pitch out loud — not in your head, out loud — and stop when the timer goes. Do this three times. It will feel uncomfortable. That discomfort is the skill building.
3. Use the Goal → Problem → Solution structure in your next Discord or team conversation.
Next time someone asks you to work on something, or you’re clarifying a brief, try mapping it: what’s the goal, what’s the problem, what’s your proposed solution? Even informally, this builds the habit.
4. Record yourself once.
You don’t need to post it anywhere. Just record a 60-second voice note of your pitch and play it back. You will immediately hear where you ramble, where you go vague, and where your energy drops. Fix those three things. Record again.
5. Apply it to your LinkedIn About section.
Your About section is a written First Minute. Rewrite the first two sentences using Context → Intent → Key Message. Who you are, what you’re building, and what you want from the people reading it.
The Bigger Picture
Every conversation you have about your work — a studio pitch, a job interview, a Discord DM, a comment on someone’s post — is an opportunity. The First Minute framework doesn’t make you a better talker. It makes you a clearer thinker. And clear thinking, communicated confidently, is what gets you the greenlight.
In the next post, we’ll go deeper into Tool 2: how to identify the professional skills you already have — even if you’ve never worked in games — and how to translate them into language the industry understands.
This post is part of a five-part series on the professional tools every game developer needs — whether you’re leaving school, changing careers, or ready to take your first project from idea to greenlight.
Nigel D'Souza 