• Open Works
  • Posts
  • šŸ–¤ Open Works #038 How To Build An Innovation Engine

šŸ–¤ Open Works #038 How To Build An Innovation Engine

Every edition we solve a people and culture problem, crowd-sourced from the Open Org community.

Welcome to Open Works. Every edition we solve a ā€˜people and culture’ problem crowd-sourced from the Open Org Community of 480+ Startup and Scale-up People Leaders.

peoplemetrics.fyi logo

This edition is sponsored by peoplemetrics.fyi–the benchmarking platform for scale-up people leaders.

Get instant access to verified data from 600+ startups and scale-ups across 18 x people and talent metrics. Gain the insights to make smarter decisions and give stakeholders the context they crave.

šŸ“šļø Recent Editions

If you’re new round here, not yet a subscriber or you straight up missed it, here are some of our recent editions.

šŸ’°ļø Edition 36: How To Think About Executive Compensation - a mental model and stage by stage guide to approach it.

šŸ”‹ Edition 35: How to Manage Change Fatigue - diagnostic, approach and framework for dealing with a real threat.

šŸ’­ This Week’s People Problem

ā

ā€œWe’re expected to constantly bring innovative ideas to our HR processes. How can we actually keep improving all the time? It feels relentless.ā€

— People | Series C | 187 People | Tech

POV: Startup People team heroically complete basic career framework…

CEO: ā€œcan we innovate more?ā€

šŸ–¤ Our Take On How You Solve

TL;DR:

Products need constant iteration.

Your people product is no different.

But innovation isn’t just about churning out endless ideas (that is exhausting!). It’s about building a repeatable engine that consistently surfaces, tests, and scales what actually works.

Innovation = input + testing + feedback.

But before you build the engine, make sure it’s pointed at the right problem. Align it with what your company stage actually needs.

The Real Problem

ā€œInnovate moreā€ is often thrown at People teams without any clarity on what that innovation is for.

And without that context, you can end up spinning:

šŸ‘‰ testing a flashy new onboarding flow when what you really need is to fix payroll
šŸ‘‰ launching a mentorship pilot when what your exec team wants is cost-per-hire savings
šŸ‘‰ adding more stuff when your team needs better basics

Before you build a system for innovation, figure out what kind of innovation matters right now.

JooBee to the rescue with a super handy mental model (i think):

Our friend JooBee made this elegant ā€œHR Hierarchy of Needsā€ framework this. Source

So…

  • If you’re in RUN, innovation focus = eliminating pain points + building reliability

  • If you’re in DRIVE, innovation focus = aligning people processes to business goals

  • If you’re in GROW, innovation focus = custom solutions that unlock performance

  • If you’re in SCALE, innovation focus = big bets and 10x plays

āš ļø Innovation without this context leads to noise. With it, you start solving the right problems at the right time.

So... How Do You Actually Build a Repeatable Innovation Engine?

You need three ingredients:

  1. Input → ideas, signals, frustrations

  2. Testing → fast, low-stakes experiments

  3. Feedback → learning loops and metrics

🧠 Build the System, Not Just the Idea

Here’s a simple innovation loop you can run monthly:

  1. Live Pain Tracker

    • Slack form or Google Form or Miro board. Anyone can log friction points across people experience.

    • Categorise monthly. Prioritise by frequency + impact.

  2. Monthly Innovation Sprint

    • Pick a theme (onboarding, feedback, L&D, etc.)

    • Assign an owner. 2 weeks to test one change.

    • Low stakes. High learning.

  3. Steal & Adapt Time

    • Every quarter, go to your community, learn something new that someone else is trying...

    • Force-fit one into a test.

  4. Test & Kill Quickly

    • If it works, scale it. If it doesn’t, kill it fast and capture what you learned.

šŸ’”Some of my favourite but simplest success metrics:
 - # of experiments/month
 - Time from idea → live test
 - % of experiments that scale

šŸ›  Remix Catalogue: Practices Worth Poaching

Got a basic loop in place and looking for ideas? I love borrowing from other disciplines here. Examples from some of my favourite below:

šŸ” From Lean Startup & Agile

Practice

Description

Remix Ideas

MVP Your People Product

Start with scrappy, testable versions of HR ideas (e.g. onboarding, 1:1 guides, recognition rituals).

Pilot new manager training with just 1 team. Use Slack or Loom instead of full LMS.

Waste Mapping

Visualise time, energy, or goodwill leakage across workflows.

Map the current performance review cycle. Ask ā€œwhat’s the most frustrating part for each group?ā€

User Interviews

Think employees = customers. Get curious about their pain points.

Run 20-minute chats with 5 people from different teams. Ask: ā€œWhen did you last feel the {theme focus} was broken?ā€

ā™»ļø From Continuous Improvement / Kaizen

Practice

Description

Remix Ideas

Small Wins Culture

Celebrate every micro-improvement. Highlight everyday experimentation.

Weekly #wins Slack thread. Reward the tiniest fix that made someone’s life easier.

Gemba Walks

Go to the place where work happens. Listen, observe, ask.

Join 1 sprint planning per team each quarter. Create ā€œwhat I noticedā€ recap journals.

Standard Work Experiments

Codify current state. Then test the smallest possible improvement.

Make a standard script for exit interviews, then A/B one tweak and observe.

šŸŽØ From Design Thinking & Innovation

Practice

Description

Remix Ideas

"How Might We…" Framing

Reframe problems to open up new solution spaces.

ā€œHow might we make performance reviews something people ask for?ā€

Rapid Prototyping

Build fast and scrappy. Test before perfecting.

Use a Notion page or Miro mockup to test a new framework.

Persona Mapping

Design for extremes: your most underserved personas.

Create personas like: ā€œFirst-time managerā€, ā€œRemote new joinerā€, ā€œBurned-out ICā€.

Experiment Backlogs

Track and prioritise ideas like a product team.

Use Trello/Notion for ā€œExperiments We’re Runningā€. Include hypothesis + success signal.

5 Whys

Go deeper than symptoms. Root cause matters.

When someone says ā€œonboarding is brokenā€, ask ā€œwhy?ā€ five times.

Next Steps

  • Pick next month’s innovation sprint theme + assign an owner.

  • Run a ā€œsteal and adaptā€ session. What’s one practice from outside you can trial?

  • Track your innovation/experiment backlog like a product team. If you don’t know how, go ask them.

šŸ“šļø Good reads and resources...

šŸ¤“ Want to Get Your Current ā€œPeople Problemā€ Featured?

Need an internet hug? Hit reply, share your challenge!

We’re here for the trickiest challenges you’ve got. Hit reply to this email, and let us know what’s keeping you up at night, and we’ll feature next time anonymously!

šŸ–¤ Psst! Did You Know We Are Launching An Exclusive Annual Content Membership For People People?!

Well my friend, now you do.

šŸ‘‰ļø Adam wrote words about this here. 

TL;DR- it’s all our past/current/future playbooks we’ve written for People People bundled up into an affordable yearly subscription (Ā£120) as well as thousands of pounds of HR tech discounts and some other free stuff.

Early bird discount of 25% off for year 1. If that sounds fun, get your name on the list here šŸ‘‡ļø 

With 🧊 & šŸ”„ 

John & Adam

šŸ‘‰ļø Know someone who’d love this newsletter? Forward it their way so they don’t miss out, and make my day whilst you’re at it! šŸ™‚ 

Reply

or to participate.