“Design is not just what it looks and feels like. Design is how it works.”
– Steve Jobs
A New Paradigm for Team Design
What if we approached teams the same way we approach the products we so carefully create – with empathy from the outset, ongoing iteration, and continuous value testing?
Conventional team structures frequently function similarly to legacy systems: they are inflexible, antiquated, and out of step with the needs of your workforce.
It is not necessary to turn people into code in order to design teams like products. It entails using deliberate design thinking to produce settings where people flourish, roles change, and results improve.
By emphasising iterative problem-solving and user empathy, IDEO – a global design and innovation company – transformed design thinking. HR and organisational leaders are now rethinking team building by embracing those same ideas.
Principle 1: Start with the User: In This Case, the Team Member
In product design, everything starts with the user. The same should apply to your team. Instead of assuming people will fit into roles, ask:
- What motivates them?
- Where do they experience friction?
- How do they prefer to work?
Similar to how a product team studies user flow, use employee journey maps, empathy interviews, and observational feedback to gain insight into your team’s experience. You can create better roles, procedures, and outcomes when you listen intently.
Principle 2: Iterate, Don’t Just Implement
Great products aren’t launched perfectly; they’re released, tested, and refined. Why should teams be any different?
Org charts are static. High-performing teams are not. Create space for regular feedback loops, retrospectives, and lightweight experiments. Test:
- Different meeting rhythms
- Ownership structures
- Collaboration rituals
Use agile methodologies not just for delivery but for how your team functions.
Principle 3: Design for Scalability, Not Just Fit
When building a product, we design it for today and for tomorrow. Teams need the same foresight.
That means thinking modularly: Are responsibilities distributed? Are decisions documented? Are we creating org debt by relying on unwritten knowledge or a few heroes?
A scalable team has redundancy, shared ownership, and built-in feedback loops. It’s resilient to growth and change.
Principle 4: Build Cross-Functional by Default
Cross-functional isn’t just a buzzword; it’s a design choice. Better decisions result from a variety of inputs, but only when they are purposefully constructed.
Take inspiration from the Spotify model:
They divide people into small, independent teams called Squads each focused on a specific goal or product area. These Squads have freedom to decide how they work, like mini start-ups.
Squads that work in similar areas are grouped into Tribes to stay connected and aligned. Meanwhile, people with similar skills, like designers, or engineers, are part of Chapters, which help them share best practices and grow in their craft, no matter which Squad they are in.
Chapters, Tribes, and Squads provide autonomy while maintaining alignment. Establish feedback systems, integrated rituals, and common OKRs (Objectives and Key Results) to facilitate function collaboration without interfering with one another. OKRs help align different departments toward shared outcomes while giving each team the autonomy to choose how they contribute, keeping collaboration productive and respectful of boundaries.
Principle 5: Design Culture Like UX
Think of culture as the user interface of your organisation. If it’s confusing, inconsistent, or misaligned with intention, people won’t know how to behave.
Design culture with the same empathy and precision as a homepage or onboarding flow.
Run usability tests on your team rituals. Measure cultural fit like you measure user satisfaction, through regular check-ins, pulse surveys, or eNPS (Employee Net Promoter Score). Then iterate.
Note: eNPS is a quick metric that asks employees how likely they are to recommend your workplace to others, acting as a barometer for engagement and cultural alignment.
Watch Out: Don’t Productise People
Here’s the caution: teams aren’t apps. You’re not optimising code; you’re building trust. Avoid these traps:
- Over-indexing on performance metrics
- Automating empathy out of the system
- Assuming standardisation works across personalities
Balance structure with flexibility. Systems thinking should serve people, not dehumanise them.
Final Thought: Design Your Team the Workday Way
Designing teams like products becomes even more powerful when they’re built for a platform like Workday.
The team you need to support Core HCM is different from the one you’ll need for Financials, Adaptive Planning, or Prism Analytics.
What would your team design look like if you started from scratch?
Just like Workday is modular and ever-evolving, your team structure should scale with your product roadmap.
- Launching a new module? You may need new roles or specialised skill-sets.
- Expanding to global payroll? You’ll need cross-functional collaboration across regions.
- Shifting to analytics or AI-based insights? Your team needs to grow beyond transactional support into strategic delivery.
Designing great teams requires more structure, experience, and strategic support as well as good intentions.
Thats where we come in.
We combine deep Workday product understanding and hiring expertise to design teams that evolve with your platform.
That means fewer bottlenecks, faster rollouts, and smarter hiring at every stage.
Our experts bring years of experience assembling high-performance Workday teams across modules, industries, and phases of growth.
Save time. Make expert hires. Build with confidence.
Let’s design a Workday team that scales with your system. Contact us us today.
