Team Performance

When you open this playbook in the Profit System, you will find:

• Action 1: Role Success Scorecard

  Define measurable outcomes for each role so everyone knows exactly what winning looks like. Clear targets make everything else possible.

  Show full action →

  Hide full action

  What to Do

  For each role in your business, define 3-5 measurable outcomes that make it clear what winning looks like. Not tasks, not activities, not job descriptions. Outcomes. The question each scorecard answers is simple: "If this person is doing a great job, what results would I see?"

  Why It Matters

  Most employees are unclear on what success actually looks like in their role. They know their tasks, they know their responsibilities, but they could not tell you the 3-5 results that define whether they are performing well. This ambiguity creates two problems. For high performers, it means they never feel a sense of achievement because the target keeps moving. For underperformers, it means problems go unaddressed because there is no clear standard to measure against.

  How to Use This

  Work through each role in the business, starting with the ones that have the biggest impact on revenue and customer satisfaction.

  ---

  Build the Scorecard

  • [ ] List every role in the business, including your own - Use actual role titles, not people's names. You are defining the role, not evaluating the person.
  • [ ] ⚡ Quick Win: For each role, write one sentence: "This role exists to..." - If you cannot finish that sentence clearly, the role itself needs clarifying before you can define success.
  • [ ] Identify 3-5 measurable outcomes for each role - Not activities ("make sales calls") but outcomes ("close £X in new revenue per month"). What results would you see if this role were being done brilliantly?
  • [ ] Set specific targets for each outcome - "Improve customer satisfaction" is not measurable. "Maintain NPS above 40" or "Resolve 90% of tickets within 24 hours" is. Every outcome needs a number.
  • [ ] Define how each outcome gets measured - Where does the data come from? Who reports it? How often? If you cannot measure it reliably, it is not a useful outcome.

  Test and Validate

  • [ ] Check that outcomes are within the role's control - A salesperson can control their pipeline activity and close rate. They cannot control whether marketing generates enough leads. Only include outcomes the role holder can genuinely influence.
  • [ ] Verify that outcomes connect to business goals - Every role scorecard should ladder up to the company KPIs. If a role's success metrics do not connect to business results, something is misaligned.
  • [ ] ⚡ Quick Win: Share the draft scorecard with the person in the role - Ask: "Does this feel fair and accurate? Is anything missing?" Their input improves the scorecard and builds buy-in at the same time.
  • [ ] Check for conflicting outcomes across roles - If sales is measured on new deals and delivery is measured on utilisation, they may be pulling in opposite directions. Resolve conflicts before publishing.

  Implement

  • [ ] Format each scorecard consistently - Role title, purpose statement, 3-5 outcomes with targets and measurement methods. Keep it to one page per role.
  • [ ] Use scorecards in your hiring process - When you recruit for a role, the scorecard tells candidates exactly what success looks like. This attracts people who want accountability.
  • [ ] Build scorecards into your performance review process - Every review conversation should start with the scorecard. How did the person perform against their defined outcomes?
  • [ ] Review scorecards every 6 months - Roles evolve. Priorities shift. Update the scorecards to reflect the current reality, not last year's expectations.
  • [ ] Display scorecards where people can see them - Not locked in an HR file. On the wall, in a shared document, or in your team wiki. Visibility reinforces clarity.

  ---

  Expected Outcome

  • Every role in the business has a clear, one-page success scorecard
  • 3-5 measurable outcomes per role with specific targets
  • Team members understand exactly what "winning" looks like in their role
  • Scorecards used in hiring, reviews, and daily management
  • Alignment between individual role outcomes and business-level KPIs

  Coach Notes

  The most common mistake is writing activity-based scorecards instead of outcome-based ones. "Send 50 emails per week" is an activity. "Generate 10 qualified leads per week" is an outcome. Keep pushing the client toward outcomes. Activities are how people choose to achieve the outcome, not the measure of success itself.

  For very small teams where people wear multiple hats, create a scorecard for the role, not the person. If Sarah handles both sales and customer service, she has two role scorecards. This makes it clear when the business is ready to split the role into two positions.

  Some clients resist putting numbers on everything. Help them see that vague expectations are unfair to the employee. "Do a good job" is not a target anyone can hit with confidence.

• Action 2: Performance Review System

  Build a structured, consistent process for regular performance discussions. Same framework, same frequency, same quality of conversation for everyone.

  Show full action →

  Hide full action

  What to Do

  Design and implement a structured, consistent process for regular performance conversations. The same framework, the same frequency, the same expectations for everyone. No more ad hoc chats that vary depending on the manager's mood or the employee's confidence. A proper system that makes performance discussions productive, predictable, and fair.

  Why It Matters

  Performance reviews have a terrible reputation, mostly because most businesses do them badly. Annual reviews that surprise people with feedback from 11 months ago. Vague conversations that end with "keep up the good work" or "try harder." The problem is not the concept. It is the execution. A well-designed review system gives people regular, honest feedback, catches problems early, celebrates progress, and creates a paper trail when difficult decisions need to be made.

  How to Use This

  Work through each step to design your review framework, then prepare for and run your first round.

  ---

  Step 1: Design the Framework

  • [ ] Set your review frequency - Quarterly is the sweet spot for most small businesses. Annual is too infrequent. Monthly is too burdensome unless your team is very new. Pick a rhythm and commit to it.
  • [ ] Choose a standard format - Every review should cover: scorecard results (how did they perform against their outcomes?), strengths demonstrated, areas for improvement, development goals, and actions for next quarter.
  • [ ] ⚡ Quick Win: Create a one-page review template - A simple document with sections matching your format. Same template for every role. Consistency makes preparation faster and comparison easier.
  • [ ] Define who reviews whom - Direct manager reviews their team members. If you are a solo founder managing everyone, that is fine for now. As you grow, this will need to cascade.
  • [ ] Build in self-assessment - Before each review, the employee fills out the same template about their own performance. This gives you their perspective before the conversation starts and often surfaces things you would have missed.

  Step 2: Prepare for Reviews

  • [ ] Gather data before the conversation - Pull scorecard results, customer feedback, project outcomes, and any notes you have made during the quarter. Reviews based on data are fair. Reviews based on memory are biased.
  • [ ] Keep a running notes file for each person - When something notable happens (good or bad), jot it down. Do not rely on remembering everything at review time. A quick note takes 30 seconds and prevents recency bias.
  • [ ] Schedule reviews in advance - Put them in the calendar 2 weeks ahead. Give the employee time to prepare their self-assessment. No ambush reviews.
  • [ ] Prepare your key messages - Go into each review knowing the 2-3 most important things you want to communicate. What is the person doing well? What needs to change? What is the most important development focus?

  Step 3: Run the Review

  • [ ] Start with the scorecard - Results first, feelings second. "Here is how you performed against your defined outcomes." This grounds the conversation in facts.
  • [ ] Discuss strengths before development areas - This is not about being soft. It is about building trust so the person can hear the constructive feedback without becoming defensive.
  • [ ] Be specific, not general - "Your client retention rate was 92%, above the 85% target" is useful. "You are great with clients" is not. Apply the same specificity to improvement areas.
  • [ ] Agree on 1-2 development goals for next quarter - Not ten. One or two. With specific actions and a timeline. These get reviewed at the next session.
  • [ ] ⚡ Quick Win: End every review with: "What do you need from me to succeed next quarter?" - This flips the power dynamic and often reveals blockers you did not know about.

  Step 4: Follow Through

  • [ ] Document the review conversation - Both parties should have a copy of what was discussed, agreed, and expected. This protects everyone.
  • [ ] Schedule a mid-quarter check-in - A 15-minute conversation halfway through to check progress on development goals and address any emerging issues. Not a full review, just a pulse check.
  • [ ] Track development goals across quarters - If someone's improvement area has been the same for three quarters, either the support is not working or the person is not the right fit. Both need addressing.
  • [ ] Act on what you learn - If multiple reviews surface the same systemic issue (poor tools, unclear processes, lack of training), fix the system. Do not keep coaching individuals around a broken environment.

  ---

  Expected Outcome

  • A consistent, structured review process that runs every quarter without fail
  • Every team member receives honest, data-driven feedback on a predictable schedule
  • Development goals set and tracked over time
  • A documented history of performance conversations for every person
  • Problems caught quarterly instead of festering until they become crises

  Coach Notes

  The number one excuse for not doing reviews is "we are too busy." Reframe it for the client: "You are too busy NOT to do reviews. Without them, you spend far more time on misalignment, underperformance, and preventable turnover."

  Help the client rehearse difficult conversations before their first round. Most managers have never been taught how to give constructive feedback. Role-play the conversation. Practice saying "Here is what needs to change and here is why" without softening it into uselessness.

  For businesses with no review history, the first round will feel awkward. That is normal. By the third quarter, it becomes routine. Encourage the client to start even if it feels imperfect. A mediocre review is better than none.

• Action 3: Development Planning

  Create clear pathways for skill building and career advancement. Map the specific capabilities, experiences, and results needed for each person to reach their next level.

  Show full action →

  Hide full action

  What to Do

  Build clear, practical development pathways for each team member that map the capabilities, experiences, and results needed to reach the next level. This is not about creating elaborate career frameworks. It is about answering one question for every person: "What do I need to learn, demonstrate, and achieve to progress here?"

  Why It Matters

  People do not leave businesses because of money alone. They leave because they cannot see a future. When there is no development pathway, ambitious people start looking elsewhere. When the pathway exists but is vague ("just keep doing a good job and we will see"), it creates frustration. A clear development plan retains your best people, improves performance across the board, and builds the bench strength you need to grow the business without doing everything yourself.

  How to Use This

  Work through the process for each team member, starting with your highest-potential people and anyone at risk of leaving.

  ---

  Step 1: Assess Current Capability

  • [ ] Map the key skills required for each person's current role - What do they need to be competent at? List 5-8 core skills.
  • [ ] Rate current proficiency for each skill - Use a simple scale: developing, competent, or advanced. Be honest. Overrating helps nobody.
  • [ ] ⚡ Quick Win: Have the team member self-assess before you rate them - Comparing their view to yours reveals blind spots on both sides and makes the development conversation much richer.
  • [ ] Identify strengths to leverage - What is this person already great at? Development is not just about fixing weaknesses. It is also about pushing strengths further.
  • [ ] Identify gaps to close - What skills are they missing or underperforming in? Prioritise the gaps that have the biggest impact on their role performance.

  Step 2: Define the Next Level

  • [ ] Describe what the next level looks like - Whether that is a promotion, expanded responsibilities, or mastery of the current role. Be specific about what changes.
  • [ ] List the capabilities needed at the next level - What skills, knowledge, and behaviours are required that they do not have yet?
  • [ ] Define the experiences needed - Some development only happens through doing. Leading a project, handling a difficult client, managing a team member for the first time. What experiences will build the capabilities they need?
  • [ ] Set the results threshold - What performance results would demonstrate readiness for the next level? "Consistently hits scorecard targets for 2+ quarters" is a clear threshold.

  Step 3: Build the Plan

  • [ ] Create 2-3 development goals per person - No more. Each goal should be specific, time-bound, and linked to a skill gap or required experience.
  • [ ] ⚡ Quick Win: Identify one development action each person can start this week - A book, a course module, a shadowing opportunity, or a stretch assignment. Momentum matters more than perfection.
  • [ ] Mix learning methods - Not everything is a training course. Include on-the-job projects, mentoring, peer learning, self-study, and real responsibility increases. The 70-20-10 rule applies: 70% of development comes from challenging work, 20% from others, 10% from formal training.
  • [ ] Assign a development sponsor or mentor - Someone other than their direct manager who can offer guidance, open doors, and provide a different perspective.
  • [ ] Set review checkpoints - Monthly or quarterly touchpoints to discuss progress, adjust the plan, and address blockers. Development plans that get set and forgotten are worthless.

  Step 4: Support and Track

  • [ ] Allocate time and budget for development - If you tell people to develop but give them no time or resources, the message is clear: it is not really a priority.
  • [ ] Track development progress alongside performance - Include development goals in your quarterly reviews. They are not separate from performance. They are part of it.
  • [ ] Celebrate progress and milestones - When someone completes a development goal or demonstrates a new capability, acknowledge it publicly. This signals that growth matters in your business.
  • [ ] Adjust plans when circumstances change - Business priorities shift, people's interests evolve, and new opportunities appear. Review and update plans at least every 6 months.

  ---

  Expected Outcome

  • Every team member has a clear, written development plan with 2-3 specific goals
  • Each person knows what capabilities, experiences, and results are needed for the next level
  • A mix of development activities scheduled and underway
  • Regular check-ins tracking progress and maintaining momentum
  • Higher retention of your best people because they can see a future in the business

  Coach Notes

  The biggest pitfall here is creating plans that are too ambitious. A development plan with 8 goals and 20 actions will overwhelm the person and get abandoned. Two or three focused goals with clear next steps are far more effective.

  Push the client to have the development conversation even if they do not have a formal career ladder or promotion pathway. Not every business needs titles and levels. But every person needs to know they are growing, valued, and heading somewhere. "You are going to get better at X, take on more responsibility in Y, and we will review where that leads in 6 months" is enough.

  For very small businesses where there is no obvious "next level" role, development can focus on mastery, expanded scope, or preparing for a future role that does not exist yet. Growth does not always mean promotion. It can mean becoming genuinely excellent at what you do.

• Action 4: Feedback Culture Toolkit

  Install the systems and skills that make candid, helpful feedback a normal part of how your team operates. Train managers to give feedback that drives improvement, not defensiveness.

  Show full action →

  Hide full action

  What to Do

  Build the systems, skills, and habits that make candid, helpful feedback a normal part of how your team operates. Not annual review feedback. Not "can I give you some feedback?" (which makes everyone tense up). Regular, in-the-moment, two-way feedback that helps people improve continuously. This action gives you the tools and frameworks to make that happen.

  Why It Matters

  In most small businesses, feedback only happens when something goes wrong. A mistake gets made, frustration builds, and eventually someone has an awkward conversation that should have happened weeks earlier. Meanwhile, good work goes unrecognised because nobody thinks to mention it. A feedback culture changes the default. When feedback is normal, problems get addressed quickly, people improve faster, and the team trusts each other more because honesty is expected, not feared.

  How to Use This

  Pick the elements that fit your team's size and maturity. Not everything here will be relevant for every business. Start with the foundations and add more as the culture develops.

  ---

  Feedback Frameworks

  • [ ] Adopt a simple feedback model for your team - SBI (Situation, Behaviour, Impact) works well. "In the client meeting yesterday [situation], when you interrupted the client twice [behaviour], it made them hesitate to share their real concerns [impact]." Teach everyone the same model.
  • [ ] Separate feedback from judgement - Feedback describes what happened and its effect. Judgement evaluates the person. "The report had three errors" is feedback. "You are careless" is judgement. Train the difference.
  • [ ] ⚡ Quick Win: Start your next team meeting with one piece of positive feedback per person - Go around the room. Each person recognises something a colleague did well this week. Takes 5 minutes, shifts the tone immediately.
  • [ ] Create a "how to receive feedback" guide - Giving feedback is hard. Receiving it is harder. Teach your team to listen, ask clarifying questions, and say "thank you" before reacting. Defensiveness kills feedback culture faster than anything.

  Manager Skills

  • [ ] Train every manager (including yourself) on delivering constructive feedback - Practice out loud. Role-play difficult conversations. Knowing a framework and using it under pressure are very different things.
  • [ ] Teach the 24-hour rule - Give feedback within 24 hours of the event. After that, the details get fuzzy, the emotion fades, and the learning opportunity passes.
  • [ ] Model vulnerability as the leader - Ask your team for feedback on your own performance regularly. "What is one thing I could do better as your manager?" When the boss asks for feedback and acts on it, everyone else feels safer doing the same.
  • [ ] Address feedback avoidance directly - If a manager is avoiding difficult conversations, coach them through it. Avoidance is the most common and most damaging feedback failure.

  Systems and Rituals

  • [ ] Build peer feedback into project wrap-ups - At the end of every project or sprint, include a 10-minute "what worked, what did not, what should we do differently?" conversation. Normalise it as part of the workflow.
  • [ ] ⚡ Quick Win: Set up a recognition channel in your team chat - A dedicated Slack or Teams channel where anyone can post a quick "thanks to [name] for [specific thing]." Low effort, high visibility.
  • [ ] Run a quarterly feedback health check - Ask the team: "How comfortable are you giving feedback? Receiving it? Is feedback happening enough?" Track the trend over time.
  • [ ] Create a "stop, start, continue" ritual - Once a quarter, each team member writes down one thing the team should stop doing, one thing to start doing, and one thing to continue. Discuss as a group.
  • [ ] Protect psychological safety - Feedback culture only works if people feel safe. If someone gives honest feedback and gets punished for it (formally or informally), the culture dies instantly. Watch for this and address it immediately.

  Scaling Feedback

  • [ ] Build feedback into your onboarding - New hires should learn on day one that feedback is expected, welcomed, and normal here. Set the expectation early.
  • [ ] Use 360-degree feedback for senior roles - For managers and leaders, gather feedback from their team, peers, and their own manager. This gives a rounded picture that self-assessment and top-down review miss.

  ---

  Expected Outcome

  • A common feedback framework that everyone in the business uses
  • Managers confident and practised in giving both positive and constructive feedback
  • Feedback happening regularly and informally, not just in formal reviews
  • A recognition system that makes good work visible
  • A team that trusts each other enough to be honest

  Coach Notes

  Feedback culture is one of the hardest things to build because it requires the business owner to go first. If they avoid difficult conversations, their managers will too. If they only give feedback when something goes wrong, the team will associate feedback with criticism. The leader sets the tone.

  Start with positive feedback. It is easier, it builds trust, and it creates the safety that makes constructive feedback possible later. A team that has never heard "great job on that" is not ready for "here is what you need to change."

  For very small teams (2-3 people), skip the formal systems and focus on the leader modelling the behaviour. Regular one-to-one conversations with honest, specific feedback will do more than any framework or Slack channel.

• Action 5: Performance Incentive Alignment

  Review and redesign how recognition, rewards, and advancement decisions get made to ensure they reinforce the behaviours and results you actually want.

  Show full action →

  Hide full action

  What to Do

  Review and redesign how recognition, rewards, and advancement decisions get made in your business to ensure they reinforce the behaviours and results you actually want. Most incentive systems were not designed. They evolved. And they often reward the wrong things or miss the right ones entirely. This action brings deliberate thinking to how you motivate, recognise, and reward your team.

  Why It Matters

  People do what they get rewarded for. If you pay salespeople purely on revenue but want them to find profitable clients, you have a misalignment. If you promote based on tenure but want high performance, you are sending the wrong signal. Incentive misalignment does not just waste money. It actively drives the wrong behaviours. When incentives are aligned with your business goals and values, the team naturally pulls in the direction you need.

  How to Use This

  Audit your current incentive structure, identify misalignments, and redesign the elements that need fixing. Not everything will need changing. Focus on the areas where misalignment is costing you the most.

  ---

  Audit Current Incentives

  • [ ] List every formal incentive in your business - Base pay, bonuses, commissions, profit share, benefits, perks, equity, promotion criteria. Get the full picture.
  • [ ] List every informal incentive - Who gets the best projects? Who gets public praise? Who gets the most flexibility? Informal incentives often drive behaviour more than formal ones.
  • [ ] ⚡ Quick Win: Ask each team member: "What gets rewarded here?" - Their answers will tell you what your incentive system actually communicates, which may be very different from what you intend.
  • [ ] Map each incentive to the behaviour it encourages - Commission on revenue encourages selling. But does it encourage selling the right things at the right price to the right customers? Follow the logic through.
  • [ ] Identify misalignments - Where are incentives encouraging behaviours that conflict with your goals? Common ones: rewarding individual performance when you need teamwork, rewarding activity when you need outcomes, rewarding short-term results when you need long-term relationships.

  Redesign for Alignment

  • [ ] Start with your business goals - What are the 3-5 results that matter most right now? Your incentive system should push people toward those results.
  • [ ] Ensure every incentivised metric connects to a business outcome - If you bonus someone on a number, that number should drive revenue, profit, customer satisfaction, or operational efficiency. If it does not, question why it is incentivised.
  • [ ] Balance individual and team incentives - Pure individual incentives create competition. Pure team incentives create free-riders. A mix (typically 60-70% individual, 30-40% team) drives both personal accountability and collaboration.
  • [ ] Include quality, not just quantity - If salespeople are bonused on deals closed but not on client retention, they will close anyone who fogs a mirror. Add a quality measure to every quantity incentive.
  • [ ] ⚡ Quick Win: Fix the single most obvious misalignment this month - There is usually one incentive that everyone knows rewards the wrong thing. Changing it sends a powerful signal that you are serious about alignment.

  Recognition and Non-Financial Incentives

  • [ ] Design a recognition programme that reinforces your values - Public acknowledgment, team awards, or spotlight features that celebrate people who demonstrate the behaviours and results you value most.
  • [ ] Make recognition specific, not generic - "Great job this month" is forgettable. "Your follow-up system brought back three clients who were about to leave, saving us £15K in annual revenue" is memorable and reinforces exactly what you want more of.
  • [ ] Create non-financial rewards that people actually value - Extra time off, flexible hours, first pick of projects, development budget, or a simple handwritten note. Often these matter more than a cash bonus.
  • [ ] Ensure advancement criteria are transparent - If people do not know what it takes to get promoted or advance, they will assume it is political. Publish the criteria. Remove the guesswork.

  Protect Against Gaming

  • [ ] For every incentive, ask: "How could someone hit this number without doing the right thing?" - If you can think of a way to game it, someone will. Build safeguards or add balancing metrics.
  • [ ] Monitor for unintended consequences - After changing incentives, watch behaviour closely for the first 2-3 months. Are people responding the way you expected? Adjust quickly if not.
  • [ ] Review incentive structure every 6 months - Business goals change. Incentives should change with them. A bonus structure from two years ago may be rewarding last year's priorities.

  ---

  Expected Outcome

  • A complete picture of every formal and informal incentive in the business
  • Misalignments between incentives and business goals identified and addressed
  • A redesigned incentive structure that rewards the right behaviours and results
  • Recognition and non-financial rewards that reinforce company values
  • Safeguards in place to prevent gaming and unintended consequences

  Coach Notes

  This is a sensitive topic because changing incentives affects people's income and perception of fairness. Advise the client to communicate changes openly and explain the reasoning. "We are aligning rewards with what matters most for the business and for customers" is much better received than silent changes people notice on their pay slip.

  If the client has commission-only salespeople, watch for the common trap where commission structure has not been updated since the business was small. What worked for a startup hustling for any revenue may be wrong for a business that needs profitable, long-term clients.

  For very small businesses without formal bonus structures, this action is still relevant. The informal incentives (who gets praise, who gets the interesting work, whose ideas get listened to) are still shaping behaviour every day. Making those informal systems intentional is just as important as designing a bonus plan.