METRICS HACKING No advanced technology? No budget? No analyst? No problem! Starting a metrics program is as easy as 1, 2, 3.
HOW…IN 1, 2, 3 EASY STEPS
WHY: YOUR BUSINESS
• Demand and capacity planning and visibility • Justify additional resources • Leverage to push back • Improve team efficiency • Build a case to invest in more advanced technology
WHY: THE BUSINESS
• Build credibility with leadership • Support data-driven decision-making • Validate resource utilization against company priorities
• Bonus: make you look really smart!
• Comments in a proof
• Person hours available
• Asset types
• Replies in a thread
• People you serve
• New requests
• With a brief or not
• Within SLA or not
• Project types
• Files/GB in repository
• Project size/LOE
• Revisions and versions
• Projects killed
• Days from in to out
• Scope creep
• More things
COUNTING TIPS, TRICKS & SOURCES
• Calendar • Email content search • Email Easter eggs • Email rules and filters • Email subject line conventions
RULES OR FILTERS
SUBJECT NAME CONVENTION
2. WRITE IT DOWN…
• IIII IIII with pen and notebook • Note app • Document • Spreadsheet • Database
• Start with a weekly cadence
3. USE IT
• Start working with what you have. • Play around and get comfortable with manipulating it. • Introduce some of your stats in relevant meetings and emails. • Try a “let me research that and get back to you with my analysis.”
WHAT & WHEN • Which client requested the most banner projects last quarter? • In how many days on average do we deliver XL projects?
WHO & HOW MANY • Total people days last week
total active projects last week = capacity index or ‘busyness’ factor
• Weekly active projects totals build trend data. When should we expect peaks and valleys?
MORE EXAMPLES • Total GB in folders or drives today
same next week = output volume, productivity rate, or yield
• Number of comments on a project in collaboration, project social, or chat tool = churn factor • Average number of days to deliver an XS, S, M, L, XL = validation of (or basis for) your SLA • Number of revisions or versions of a proof before approval > identify trouble areas, or inform future timelines • Be creative! Define your own indexes and measures to target your biggest challenges.
2. WRITE IT DOWN…FAITHFULLY
3. USE IT
• This is just the beginning! Keep following all three steps. • Look for ways to automate steps one and two. • Go make the case to your leadership that you need a technology solution. You have proof of concept that you’re ready! • Evolve beyond outputs metrics, and start experimenting with input, performance, and outcome metrics. • Share your journey with the creative operations community so we can learn from you one day!
Photo credits: Slide 2, #54985127 © pressmaster / Adobe Stock. Slide 3, #169189287 © leonidkos / Adobe Stock. Slide 7, ”count” by Barry Stock is licensed under CC BY-SA 2.0. Slide 13, “Plimpton 322” is in the public domain. Slide 15, “James E. Church in 1920,” is courtesy of University of Reno, Nevada and licensed under CC BY-SA 2.0 and Figure 10, is courtesy of United Sate Department of Agriculture, Natural Resources Conservation Service. Slide 16, #19648162 © FocalPoint / Adobe Stock. Slide 23, #175057150 © Sunny studio / Adobe Stock.