top of page

Value by Design: Designing for Change, Value and Adoption From Day One

When organisations talk about HR technology transformation, they often focus on the system. The features. The workflow. The timeline. All important, of course, but none of those things guarantee impact. What really makes a difference is how intentionally you design for people, for change and for measurable value right from the start.


This is the heart of our Value by Design framework. It is not a document. It is not a project phase. It is a way of thinking that shapes every conversation and every decision across the life of a project. Value by Design is built on three principles: design the vision, design the experience, and design the proof. This article focuses on the first, how you create clarity and alignment from day one.


In this first article of our Value by Design series, we want to set out what that framework looks like and why it is becoming essential for HR and TA leaders who want more than a successful go-live: they want a successful transformation.


A Real-world Example: Struggling Without a Baseline

Recently, an enterprise client had a strong technical launch, with positive feedback from users and a well-coordinated go-live plan. The challenge came six months later when the organisation asked for ROI. The team suddenly realised that no one had defined success in measurable terms at the start. There was no clear baseline from before implementation. They spent weeks searching for historical data and debating which metrics mattered.


In the end, the story was incomplete because the foundation had not been set early. The lesson was clear. If you do not define value and baseline it before build, you cannot credibly demonstrate impact later, no matter how well the technology performs.


The Value by Design framework

The Value by Design framework consists of 5 pillars which help you avoid this situation. Here’s how it works.


Value by Design framework

Define Value Early

One of the simplest and most powerful steps you can take happens before the project even begins. Write one sentence that describes what success looks like. Not a paragraph full of qualifiers. Not a list of ten KPIs. Just a clear statement that completes the idea:


We will know this project worked if...


This sentence becomes the anchor for everything that follows. It forces clarity about the outcome you want, not the activity you plan to complete. It also gives your project team a shared language. When HR, IT and business leaders all point to the same sentence, decision making becomes far easier.


Where teams often stumble is in trying to define value after the build. By then it is too late. Without a baseline and a shared definition of success, value becomes something you talk about rather than demonstrate


Integrate Change From Day One

If there is one habit that separates high performing project teams from the rest, it is the way they treat change. They do not see it as a final training sprint or a separate workstream. They weave it into everything.


Discovery becomes a chance to understand how people feel today, not just what they do. Design becomes a chance to test messages, not just screens. Testing becomes a chance to bring in champions early, not wait until the end. When you build this rhythm from the beginning, adoption becomes a natural outcome rather than something you have to push.


Stakeholder alignment is also part of this early work. If you wait until the requirements gathering phase to engage stakeholders, you are already behind. People form opinions quickly. They want to know the vision and the why. Including them early helps you prevent resistance before it forms.


Don’t Separate People, Process & Technology

One of the biggest risks in HR technology projects is siloed ownership. HR writes the process. IT builds the system. Communications appear near the end with a launch plan. This separation might feel efficient in theory, but in practice it creates misalignment that shows up the moment people start using the new solution.


A Value by Design mindset brings these groups together from day one. Every decision considers how the system works, how the process flows and how people need to move through it. It means your roadmap is not three parallel documents but one integrated plan with shared accountability. When these elements move together, you build something that fits not only technically but behaviourally.


Use Governance to Create Confidence

Good governance does more than protect the project. It builds trust. In every phase, you should ask three simple questions.

  1. What value have we unlocked so far?

  2. What risks could affect adoption?

  3. How is the business demonstrating engagement right now?


These questions turn a steering committee from a status call into a meaningful conversation about impact. I have seen project sponsors shift their entire relationship with technology delivery just by embedding these questions. Suddenly the project is not only about configuration and timelines. It becomes about outcomes, readiness and confidence. When leaders see progress in these terms, momentum builds naturally.


Value Proof Over Perfection

There is a common belief that you should wait for the system to be perfect before sharing anything about progress. In reality, early proof is far more valuable than a perfect launch story.


Share small wins as they happen. Share early feedback, even if it is mixed. Share examples of champions who are already embracing the new approach. These moments build credibility. They give people a reason to believe in the work. They also help you shape the narrative inside the organisation long before the big reveal.


The Key Do’s and Don’ts

The Value by Design mindset is practical. Here are straightforward actions you can take.


DO

  • Bring your change and adoption leads into the project from the beginning so they can shape the experience, not just explain it.

  • Start with two or three business outcomes that everyone understands and cares about.

  • Share small wins throughout implementation to create visibility and excitement.

  • Create a visible one-page Value by Design that captures outcomes, owners and measures. Keep it in front of the team.

  • Activate champions early, well before UAT, so they can influence design and build credibility.


DON'T

  • Treat change as training that happens in the final week before launch.

  • Wait until after the system is built to define what success looks like.

  • Limit progress updates to steering committees instead of communicating impact to the wider organisation.

  • Hide your Value by Design inside a project deck. If no one sees it, it cannot guide decisions.

  • Introduce champions after the solution is already finished because their influence will come too late.


Common Pitfalls To Avoid

There are patterns that show up again and again in HR technology delivery. Leaders often talk confidently about value, yet struggle to describe what it means in practical, measurable terms. Without that clarity, the project becomes a series of tasks instead of a journey toward an outcome.


Adoption metrics also suffer from unclear ownership. Everyone assumes someone else will measure success. When launch day arrives, no one is positioned to track how the organisation is actually experiencing the change.


Stakeholder alignment is another challenge. HR might be looking at process efficiency, IT at system performance and executives at cost or speed. When these perspectives are not aligned early, people end up celebrating different things and questioning each other’s priorities.


And finally, change is often introduced too late. By the time communications begin, the organisation has already formed its own narrative. People feel excluded and adoption slows down.


What’s next?

Here are practical steps you can take this week.

  1. Draft your one-sentence definition of success and discuss it with your project team.

  2. Identify your top five stakeholders and write down what success means for each of them.

  3. Choose three metrics you can baseline now, even if the data is rough.

  4. Add a value review item to your next steering meeting agenda.

  5. Share one early win with the business to generate positive energy.


A Real-world Success Story

Remember that cautionary tale at the start of the article? Well, here’s an example of a client that utilised the Value by Design mindset to build momentum early. On one recent Talent Tech project, we made a simple shift in how the team approached governance. At every milestone, we asked three questions.

  1. What value have we delivered so far?

  2. What could affect adoption if we do not address it now?

  3. How is the business demonstrating engagement right now?


These questions changed the entire rhythm of the project. Steering meetings became conversations about impact rather than slide decks. The team shared small wins as they happened, which built confidence long before go-live. Champions were activated early and shaped parts of the design. When launch day arrived, adoption moved quickly because people already understood the why and could see the progress that had led there. The project avoided the typical post-launch dip and reached steady state faster than expected.


Conclusion

Transformation is not something that happens at go‑live. It is shaped through hundreds of small decisions that happen long before anyone logs in to a new system. When you adopt a Value by Design mindset, you shift the focus from delivering technology to delivering value. You give your teams clarity, you build confidence early, and you create the conditions for real adoption. Most importantly, you set your organisation up to show the impact of your investment in a way that is meaningful and measurable.


In the next article of our Value by Design series, we’ll explore how to design the experience, where people, process, and progress come together to create confidence and adoption.


If you need support in building this mindset into your next project or want help assessing where value can be unlocked in your current tech stack, we would be happy to talk. Reach out any time to discuss your goals, your challenges, or your upcoming plans. TalentTech is here to help you design for value from day one.



Comments


bottom of page