A Taste for KPI Coffee

 Lifted from here is a great excerpt analogy on what KPIs are. 



"Terminology Example: 

Let’s say someone wants to use KPIs to help them lose weight. Their actual weight is a lagging indicator, as it indicates past success, and the number of calories they eat per day is a leading indicator, as it predicts future success. 

If the person weighs 250 lbs / 113 kg (a historical trend is called a baseline), and a person they would like to emulate is 185 lbs / 84 kg (comparison research is called benchmarking), they might set an 1,700 calorie-per-day target (desired level of performance) for the leading KPI in order to reach their lagging KPI target of 185 lbs / 84 kg by the end of a year.


Let’s say my business provides coffee for catered events. Some inputs include the coffee (suppliers, quality, storage, etc.), the water, and time (in hours or employee costs) that my business invests. My process measures could relate to coffee making procedure or equipment efficiency or consistency. Outputs would focus on the coffee itself (taste, temperature, strength, style, presentation, accessories, etc.). And desired outcomes would likely focus on customer satisfaction and sales. Project measures would focus on the deliverables from any major improvement projects or initiatives, such as a new marketing campaign." 

Comments

Post a Comment

Popular posts from this blog

XP: Card, Conversation, Confirmation - The three C's

Image
  This is a technique lifted from XP (Extreme Programming).  Card On each card is enough text that identifies a requirement. Notes of priority and cost are written on it as well. They serve as tokens for requirements and are handed to developers during implementation and returned to customers when completed. Conversation  Conversations are collectively exchanges of thought between customers and programmers. It is largely verbal, but may be communicated with supplemental examples. Confirmation Confirmation, in other words, acceptance tests, are defined at the start with the customer and shown to customer at the end of the iteration to confirm the story's completion. Note that extra documentation, while seemingly helpful, hardly "confirms" anything and cannot replace acceptance tests. 
Read more

Notes: 10 Knowledge Areas of Project Management (PMBOK 6)

Image
 Notes from here  There are 10 knowledge areas, as outlined in PMBOK 6, that are to be remembered sequentially. It is presented in logical order (with exception to Stakeholders which is tacked on at the end).  Integration: In other words, you can’t ‘do’ schedule management and ignore what the impacts of that might be on people, risk, communications, cost and the rest. Scope: Knowing what the project will deliver Schedule: all about making a detailed plan to tell everyone when the project will deliver what is in the requirements. Cost: Managing project fund Quality: Although quality varies project to project and many aren't as regimented, it is important to be aware and use appropriately Resource: Working out the resources needed to get the project done Communication: Creating a communication plan and monitoring for adjustments Risk: Covers an adequate overview of managing risks  Procurement: Depending on any purchases involved, there is a lot of contracting and negotiation Stakehol
Read more

RACI Definitions

Image
Notes from site RACI is a matrix to properly organize and define stakeholders' responsibilities in the project. While there are many methods in creating these organizations, this is just one method. Definitions should be kept nearby and the charts should be clear.  Responsible: This team member does the work to complete the task. Every task needs at least one Responsible party, but it’s okay to assign more. Accountable: This person delegates work and is the last one to review the task or deliverable before it’s deemed complete. On some tasks, the Responsible party may also serve as the Accountable one. Just be sure you only have one Accountable person assigned to each task or deliverable. (Note: It might not be your PM!) Consulted: Every deliverable is strengthened by review and consultation from more than one team member. Consulted parties are typically the people who provide input based on either how it will impact their future project work or their domain of expertise on the del
Read more