- Home
- Team Tactics
- Team Strategy
Team Strategy
Table of contents

What is Team Strategy?
Team Strategy is a card from the Team Tactics deck by Pip Decks.
Aligning your team’s strategy to existing company goals is not only important, but essential for the organisation to pull in the same direction. When the direction is clear, you’re happy, your team is happy, and so is your organisation.
“A goal without a plan is just a wish.”, Antoine de Saint-Exupéry
Try Get Buy-In beforehand to hear people’s concerns. Use Agile Comms and Lean Presentations to communicate as you go.
When to use Team Strategy
- Team misalignment with company goals
- High levels of micromanagement
- Lack of team autonomy
- Frequent project delays due to unclear objectives
- Low team motivation and engagement
- Scaling challenges in growing organizations
- Confusion about roles and responsibilities
How to use Team Strategy
- Write down a change you want to see within your team. For example: more thorough design/engineering handovers.
- List the most immediate tasks you could do to create that change. For example: invite engineers to Design Crits.
- What will be different once things have changed? What are two of the benefits (‘whys’) of the tasks you listed? For example: we’ll spot issues earlier, cutting down on repeat work.
- How will this change the course of your team? What’s the outcome of the two benefits you listed? For example: improve internal collaboration to give us more time to focus on what matters.
- Summarise your responses to steps 1–4 in the following order. Use Write In Plain English to help.
- What’s the desired end-state? (E.g., great collaborative environment so we can focus on what matters to our users.)
- What will be different? (E.g., minimal repeat work.)
- What needs to change? (E.g., improve design/engineer hand overs.)
- How will we do it? (E.g., invite devs to Design Crits.)
- Follow up by setting OKRs. Use Decision Stack for further alignment and Force-Field Analysis for feasibility.






