Transforming Performance Measurement with Human-Centric Goal-Setting Frameworks

Team unity shines as a group celebrates a win with a fist bump.

Traditional Key Performance Indicators (KPIs) often focus on steady-state tracking, measuring ongoing business health through numbers and metrics. While KPIs provide valuable data insights, they sometimes miss the bigger picture of growth, creativity, and collaboration that leadership teams strive for today. Leadership is about enablement rather than just oversight. Shifting from rigid KPI tracking to more human-centred goal-setting frameworks can unlock ambitious growth, human qualitative value, and build stronger support within teams.

by Lucas Gabriel ©2024

This post explores how teams and leaders can transform performance measurement by adopting frameworks like OKRs, MBO, and KRAs. These approaches emphasise clear, inspiring goals, collaborative processes, and broad areas of responsibility, helping teams move beyond routine metrics toward meaningful, empowered progress.

Traditional KPIs: The Compass, Not the Destination

Before moving into more fluid frameworks, it is important to understand what Key Performance Indicators (KPIs) are. Traditionally, KPIs are the "health monitors" of a business, essential for tracking Business as Usual (BAU) and ensuring the ship is heading in the right direction.

A few Common KPIs include:

• Finance: Monthly Recurring Revenue (MRR) or Return on Investment (ROI).

• Marketing: Pay-Per-Click (PPC) performance or Conversion Rates.

• Retention: Churn Rate (the percentage of customers leaving).

• Support: Average Resolution Time (for help tickets).

While these are vital as a business compass—helping leaders find areas of focus or signify wins—they are rarely a great metric for individual performance. When we treat humans like an engine for corporate financial growth, we risk losing the very value they were hired to create.

Why KPIs Aren't Always the Best Option

KPIs are excellent for tracking the "what," they often fail to capture the "how" and the "why."

• They are Backward-Looking: KPIs tell you what happened in the past. They don't inspire innovation; they only report on the status quo.

• The "Checkbox" Mentality: Rigid KPIs often lead to employees "gaming the system." When a person's contribution is reduced to a number, they focus on hitting the target rather than delivering genuine value or solving problems. In my experience, this can lead to disengaged, apathetic, and sometimes overstressed staff who are simply performing tasks rather than contributing engaged, creative insight.

• Lack of Context: A KPI might show that website traffic is down, but it won't tell you if your team is currently pivoting to a higher-quality audience—a move that adds long-term value despite the short-term dip in numbers.

• The Managerial Blind Spot: When a manager focuses only on numbers rather than feedback and growth, it creates a distorted view of the role. This disconnect leads to friction, resentment, and a "robot/resource" culture.
  

An engaged creative team taking a selfie

Agile Leadership: From "Manager" to "Enabler"

Moving beyond metrics requires a shift in leadership philosophy. In an Agile environment, a leader's primary responsibility is not to police the numbers but to remove blockers and enable the team to achieve its goals.

This transformation happens in the "rhythm" of the work:

The Power of the weekly standup

The standup isn't just a status update; it's a synchronisation point. It is the heartbeat of the team's KRAs and OKRs. While many view the "WIP" (Work in Progress) as a dry weekly check-in, an Agile approach transforms it into an engine for momentum.

To keep your standups impactful, consider these principles:

• The 15-Minute Rule. Tight constraints (7 to 15 minutes) keep energy high and focus sharp. This isn't the time for deep-dives; it's the time for alignment.

• Ditch the "Tickbox" Mentality. Your PMS or CRM tracks the "what." The standup is for the "how." Avoid reading lists that could have been an email.

• Identify Connections. In a multidisciplinary environment, this is where the magic happens. Look for overlaps, dependencies, and potential clashes between creative, marketing, and product.

• Surface the Blockers. Instead of asking "Is it done yet?", an Agile leader asks, "What is stopping you from moving forward today?"

• Take it "Offline." Use the standup to identify where a deeper dialogue is needed, then schedule a separate "sidebar" for those involved. This respects everyone's time while ensuring no issues are overlooked.

By shifting the focus from "what I did" to "how we move together," the standup becomes a space where teams proactively support one another rather than just reporting to a manager.

Redefining the 1:1

To truly support human-centred growth, 1:1 meetings should move away from tactical "to-do lists" and toward empowerment-focused conversations.

Try shifting the dialogue with these four pillars:

1. What is the purpose of your work right now?

   Help the team member connect their daily tasks to the bigger picture. When someone understands the value they aim to deliver to the customer or the team, they are more empowered to make creative decisions.

2. What excites you right now?

   Uncover the intrinsic motivation that drives high-quality work. Passion is a better predictor of success than any rigid metric.

3. Where are you feeling friction?

   Identify blockers before they impact the KPIs. This allows you to address systemic issues rather than just treating the symptoms of a missed target.

4. How can I better support your work this week?

   This flips the hierarchy, making the leader a resource for the employee. It reinforces the Agile principle that leadership exists to enable the team, not the other way around.

By focusing on the person behind the project, leaders create a culture where the goals aren't just met—they are exceeded with enthusiasm.

Goal-setting frameworks visualised on a whiteboard.

How to Use OKRs to Drive Ambitious Growth

Objectives and Key Results (OKRs) differ from traditional KPIs by focusing on aggressive, time-bound goals rather than steady-state monitoring. An Objective is a clear, inspiring goal that motivates teams, such as "Become the market leader in customer experience." The Key Results are measurable steps that track progress toward the objective, such as increasing customer satisfaction scores by 20% or launching three new product features within six months.

Steps to Implement OKRs

• Set inspiring objectives that challenge the team while remaining achievable within a defined timeframe.

• Define measurable key results that clearly indicate progress toward the objective.

• Align OKRs across teams so marketing, creative, and product groups work toward shared goals.

• Review progress regularly in leadership meetings to adjust efforts and celebrate milestones.

• Encourage transparency by sharing OKRs openly within the organisation to build accountability.

  
  

Example in Practice

A marketing team aiming to increase brand awareness might set an objective to "Expand brand reach in new markets." Key results could include:

• Launching targeted campaigns in three new regions.

• Increasing website traffic from those regions by 30%.

• Securing 10 media mentions in local publications.

  
  

This approach pushes teams to think beyond maintaining current performance and focus on growth opportunities.

How to Use MBO for Collaborative Goal Setting

Management by Objectives (MBO) centres on collaboration between managers and employees to set specific, agreed-upon goals. Unlike KPIs that often track ongoing metrics, MBO focuses on milestones and outcomes that matter to both parties.

Steps to Implement MBO

• Hold goal-setting meetings where managers and employees discuss and agree on objectives.

• Define clear milestones that mark progress toward goals.

• Provide ongoing support and feedback to help employees overcome challenges.

• Evaluate performance based on milestone achievement rather than just numbers.

• Adjust goals as needed to reflect changing priorities or new insights.

  
  

Example in Practice

A creative team member working on a product launch might collaborate with their manager to set goals such as:

• Completing initial design drafts within four weeks.

• Receiving stakeholder feedback by week six.

• Finalising creative assets two weeks before launch.

  
  

This process builds trust and ensures goals reflect both organisational needs and individual capabilities.

Collaborative goals and notes in a team meeting

How to Use KRAs to Clarify Roles and Responsibilities

Key Result Areas (KRAs) define the broad responsibilities of a role, providing a high-level overview of what is expected to be delivered. KRAs help leadership and teams focus on outcomes before drilling down into specific metrics or KPIs.

Steps to Implement KRAs

• Identify core responsibilities for each role within the team or department.

• Communicate these areas clearly to employees so they understand their main focus.

• Use KRAs as a foundation for setting specific goals or KPIs later.

• Review KRAs regularly to ensure they remain relevant as roles evolve.

• Support employees in managing their KRAs through training and resources.

  
  

Example in Practice

For a customer support manager, KRAs might include:

• Ensuring high customer satisfaction.

• Managing support team performance.

• Improving response times.

• Implementing new support tools.

  
  

By focusing on these broad areas, the manager can prioritise efforts, and leadership can evaluate success beyond just numbers. KRAs describe the broad areas of outcomes for which an individual or team is accountable. They serve as a roadmap for responsibility (e.g., "Customer Satisfaction" or "Revenue Generation") rather than a list of skills or tools.

• Capability/Skill Chart: This maps your team's competencies and strengths (e.g., "Graphic Design," "Python coding"). It tells you if you have the skills required, but not necessarily the accountability for the results.

• Resource Analysis: This is about supply and demand. It assesses your available assets—budget, tools, and people—to determine whether you have enough "fuel" to reach your goals.

How They Work Together

In an Agile leadership context, you use them as a "check and balance" system:

1. KRA: "We are responsible for High-Quality Design." (The Outcome)

2. Capability Chart: "Do we have enough senior designers to do this?" (The Skill)

3. Resource Analysis: "Do they have the time and software to do it this week?" (The Capacity)

When you ask in a 1:1, "Where are you feeling friction?", you are often uncovering a mismatch where the KRA (responsibility) is high, but the Resources or Capabilities are missing.

How to facilitate human-centric goal setting

Leadership is about providing the infrastructure for success. You don't need a massive budget; you need to remove friction while building a clear, documented path for accountability.

1. Audit and Unlock Existing Resources

• Before requesting new budgets, consult with HR or other department heads to identify existing internal programs.

  • Reasoning: Many organisations have resources—training credits, L&D platforms, or mentor programs that are underutilised. Leveraging these allows you to support team growth without increasing overhead, proving your efficiency as a manager.

2. Protect "Thinking Space"

• Facilitate "Meeting-Free Blocks" to allow for deep work.

  • Reasoning: Ambitious OKRs require cognitive headspace. By protecting their schedule, you signal that you value output and quality over mere "attendance" or "participation." This shift reduces burnout and increases the ROI on the team’s time.

3. Proactive Cross-Departmental Alignment

• Don't wait for a project to "go wrong." Grab a coffee with leads in Marketing, Creative, or Product and ask: "What are your team's big goals, and how can we support them?"

  • Reasoning: This simple gesture kills silos before they start. It identifies dependencies early, preventing the "blame game" later on and ensuring that multidisciplinary teams aren't working at cross-purposes.

4. Rewrite the Review Script

• In your next check-in, spend the first 10 minutes on Capability. Ask: "What skill do you want to master this quarter?" and bake it into their KRAs.

  • Reasoning: Aligning personal growth with business needs increases retention. It transforms the manager from a "judge" into a "coach," the core of effective change management, and builds the transparency needed for high-trust teams.

5. Normalise "The Mini-Retro"

• If a goal is missed mid-cycle, host a casual 20-minute Agile Retrospective: What went well? What didn't? What do we change tomorrow?

  • Reasoning: This keeps momentum high and prevents the "heavy" feeling of a post-mortem. It enables real-time course correction, ensuring a minor setback doesn't turn into a failed project.

6. Be the "Chief Blocker-Remover"

• Close every 1:1 with: "What can I take off your plate or who can I talk to for you this week?"

  • Reasoning: This is the ultimate "Firefighter" move. Your job is to clear the path so they can run. It establishes you as a leader who provides active support, making it easier to hold the team accountable for their results later.

The Strategic Necessity of Frameworks

It is a hard part of leadership that is rarely discussed: the complexity of navigating a performance mismatch. Whether a team member is struggling due to a lack of guidance, a need for neurodiverse-friendly processes, or a poor fit within a team or organisation, the stakes are high. Without an objective framework, these complex situations can significantly impact team morale and organisational resources.

At a high level, these goal-setting frameworks are not just about driving performance; they are fundamental risk-management strategies.

Using OKRs or KRAs as the foundation for performance management provides a professional safeguard for everyone involved:

• Organisational Protection: It ensures the business has a documented, transparent history of expectations and support. This is vital for mitigating liability and ensuring that HR and Executives have the objective data they need to support difficult decisions.

• Leader Accountability: It moves the manager's role from "subjective judge" to "objective facilitator." It provides a clear framework to justify your strategy and the resources you allocate to your team.

• Employee Fairness: By defining success through a clear framework, you provide a fair and level playing field. It ensures that every team member, regardless of their background or working style, understands exactly what is required to succeed.

Ultimately, these frameworks aren't just about "hitting the target"—they are about building a robust, sustainable organisation where progress is measurable, and the professional interests of the company and its people are equally protected.

The leadership team is discussing goal-setting frameworks around a table.

Transforming performance measurement means moving beyond routine KPI tracking to embrace goal-setting frameworks that focus on ambition, collaboration, and clear responsibility. OKRs push teams to set bold, measurable goals within timeframes. MBO builds trust through collaborative goal setting and milestone tracking. KRAs clarify broad responsibilities, helping teams focus on what matters most. By providing a space that allows humans to be humans—focusing on purpose and removing blockers—you build empathy and trust. This isn't just a "nice-to-have "; it's the foundation of a sustainable business. When people feel supported rather than just monitored, they move from being a "cog in an engine" to being active partners in the company's success.