February 20, 2024
3 min

Meera Pankhania: From funding to delivery - Ensuring alignment from start to finish

Optimal Workshop

It’s a chicken and egg situation when it comes to securing funding for a large transformation program in government. On one hand, you need to submit a business case and, as part of that, you need to make early decisions about how you might approach and deliver the program of work. On the other hand, you need to know enough about the problem you are going to solve to ensure you have sufficient funding to understand the problem better, hire the right people, design the right service, and build it the right way. 

Now imagine securing hundreds of millions of dollars to design and build a service, but not feeling confident about what the user needs are. What if you had the opportunity to change this common predicament and influence your leadership team to carry out alignment activities, all while successfully delivering within the committed time frames?

Meera Pankhania, Design Director and Co-founder of Propel Design, recently spoke at UX New Zealand, the leading UX and IA conference in New Zealand hosted by Optimal Workshop, on traceability and her learnings from delivering a $300 million Government program.

In her talk, Meera helps us understand how to use service traceability techniques in our work and apply them to any environment - ensuring we design and build the best service possible, no matter the funding model.

Background on Meera Pankhania

As a design leader, Meera is all about working on complex, purpose-driven challenges. She helps organizations take a human-centric approach to service transformation and helps deliver impactful, pragmatic outcomes while building capability and leading teams through growth and change.

Meera co-founded Propel Design, a strategic research, design, and delivery consultancy in late 2020. She has 15 years of experience in service design, inclusive design, and product management across the private, non-profit, and public sectors in both the UK and Australia. 

Meera is particularly interested in policy and social design. After a stint in the Australian Public Service, Meera was appointed as a senior policy adviser to the NSW Minister for Customer Service, Hon. Victor Dominello MP. In this role, she played a part in NSW’s response to the COVID pandemic, flexing her design leadership skills in a new, challenging, and important context.

Contact Details:

Email address: meera@propeldesign.com.au

Find Meera on LinkedIn  

From funding to delivery: ensuring alignment from start to finish 🏁🎉👏

Meera’s talk explores a fascinating case study within the Department of Employment Services (Australia) where a substantial funding investment of around $300 million set the stage for a transformative journey. This funding supported the delivery of a revamped Employment Services Model, which had the goal of delivering better services to job seekers and employers, and a better system for providers within this system. The project had a focus on aligning teams prior to delivery, which resulted in a huge amount of groundwork for Meera.

Her journey involved engaging various stakeholders within the department, including executives, to understand the program as a whole and what exactly needed to be delivered. “Traceability” became the watchword for this project, which is laid out in three phases.

  • Phase 1: Aligning key deliverables
  • Phase 2: Ensuring delivery readiness
  • Phase 3: Building sustainable work practices

Phase 1: Aligning key deliverables 🧮

Research and discovery (pre-delivery)

Meera’s work initially meant conducting extensive research and engagement with executives, product managers, researchers, designers, and policymakers. Through this process, a common theme was identified – the urgent (and perhaps misguided) need to start delivering! Often, organizations focus on obtaining funding without adequately understanding the complexities involved in delivering the right services to the right users, leading to half-baked delivery.

After this initial research, some general themes started to emerge:

  1. Assumptions were made that still needed validation
  2. Teams weren’t entirely sure that they understood the user’s needs
  3. A lack of holistic understanding of how much research and design was needed

The conclusion of this phase was that “what” needed to be delivered wasn’t clearly defined. The same was true for “how” it would be delivered.

Traceability

Meera’s journey heavily revolved around the concept of "traceability” and sought to ensure that every step taken within the department was aligned with the ultimate goal of improving employment services. Traceability meant having a clear origin and development path for every decision and action taken. This is particularly important when spending taxpayer dollars!

So, over the course of eight weeks (which turned out to be much longer), the team went through a process of combing through documents in an effort to bring everything together to make sense of the program as a whole. This involved some planning, user journey mapping, and testing and refinement. 

Documenting Key Artifacts

Numerous artifacts and documents played a crucial role in shaping decisions. Meera and her team gathered and organized these artifacts, including policy requirements, legislation, business cases, product and program roadmaps, service maps, and blueprints. The team also included prior research insights and vision documents which helped to shape a holistic view of the required output.

After an effort of combing through the program documents and laying everything out, it became clear that there were a lot of gaps and a LOT to do.

Prioritising tasks

As a result of these gaps, a process of task prioritization was necessary. Tasks were categorized based on a series of factors and then mapped out based on things like user touch points, pain points, features, business policy, and technical capabilities.

This then enabled Meera and the team to create Product Summary Tiles. These tiles meant that each product team had its own summary ahead of a series of planning sessions. It gave them as much context (provided by the traceability exercise) as possible to help with planning. Essentially, these tiles provided teams with a comprehensive overview of their projects i.e. what their user needs, what certain policies require them to deliver, etc.  

Phase 2: Ensuring delivery readiness 🙌🏻

Meera wanted every team to feel confident that we weren’t doing too much or too little in order to design and build the right service, the right way.

Standard design and research check-ins were well adopted, which was a great start, but Meera and the team also built a Delivery Readiness Tool. It was used to assess a team's readiness to move forward with a project. This tool includes questions related to the development phase, user research, alignment with the business case, consideration of policy requirements, and more. Ultimately, it ensures that teams have considered all necessary factors before progressing further. 

Phase 3: Building sustainable work practices 🍃

As the program progressed, several sustainable work practices emerged which Government executives were keen to retain going forward.

Some of these included:

  • ResearchOps Practice: The team established a research operations practice, streamlining research efforts and ensuring that ongoing research was conducted efficiently and effectively.
  • Consistent Design Artifacts: Templates and consistent design artifacts were created, reducing friction and ensuring that teams going forward started from a common baseline.
  • Design Authority and Ways of Working: A design authority was established to elevate and share best practices across the program.
  • Centralized and Decentralized Team Models: The program showcased the effectiveness of a combination of centralized and decentralized team models. A central design team provided guidance and support, while service design leads within specific service lines ensured alignment and consistency.

Why it matters 🔥

Meera's journey serves as a valuable resource for those working on complex design programs, emphasizing the significance of aligning diverse stakeholders and maintaining traceability. Alignment and traceability are critical to ensuring that programs never lose sight of the problem they’re trying to solve, both from the user and organization’s perspective. They’re also critical to delivering on time and within budget!

Traceability key takeaways 🥡

  • Early Alignment Matters: While early alignment is ideal, it's never too late to embark on a traceability journey. It can uncover gaps, increase confidence in decision-making, and ensure that the right services are delivered.
  • Identify and audit: You never know what artifacts will shape your journey. Identify everything early, and don’t be afraid to get clarity on things you’re not sure about.
  • Conducting traceability is always worthwhile: Even if you don’t find many gaps in your program, you will at least gain a high level of confidence that your delivery is focused on the right things.

Delivery readiness key takeaways 🥡

  • Skills Mix is Vital: Assess and adapt team member roles to match their skills and experiences, ensuring they are positioned optimally.
  • Not Everyone Shares the Same Passion: Recognize that not everyone will share the same level of passion for design and research. Make the relevance of these practices clear to all team members.

Sustainability key takeaways 🥡

  • One Size Doesn't Fit All: Tailor methodologies, templates, and practices to the specific needs of your organization.
  • Collaboration is Key: Foster a sense of community and collective responsibility within teams, encouraging shared ownership of project outcomes.

Publishing date
February 20, 2024
Share this article

Related articles

min read
How to lead a UX team

As the focus on user-centered design continues to grow in organizations around the world, we’ll also need effective leaders to guide UX teams. But what makes a great UX leader?

Leadership may come as naturally as breathing to some people, but most of us need some guidance along the way. We created this article to pull together a few tips for effectively running UX teams, but be sure to leave a comment if you think we’ve missed anything. After all, part of what makes a great leader is being able to take feedback and to learn from others!

The difference between a manager and a leader

There’s a pretty clear distinction between managers and leaders. As a leader, your job isn’t necessarily to manage and tell people what to do, but instead to lead. You should enable your team to succeed by providing them with the tools and resources they need.

Know your team’s strengths and weaknesses

Intel’s Andy Grove, who infamously ruled the Silicon Valley semiconductor company with an iron fist, may be a polarizing figure in the leadership sphere, but he did institute (or at least help popularize) some techniques that are still widely practised today. One of these was to sit in an office cube with his fellow employees, instead of in a siloed office by himself. There’s a good lesson here. Instead of sealing yourself away from your team, immerse yourself in their environment and their work. You’ll develop a much better understanding of the types of problems they deal with on a daily basis and as a result be in a better position to help them.

You can also take this a step further and conduct an audit of your team’s strengths and weaknesses. Also known as a skills audit, this process is more commonly performed in organizations at scale, but it’s a good way to show you where your capabilities lie – even in small teams. With an intimate understanding of your UX team you’ll be in a good position to assess which projects your team can and can’t take on at any given time.

Taking this process even further, you can undertake a skills audit of yourself. If you want to develop yourself as a leader, you have to understand your own strengths and weaknesses.

This quote by Donald Rumsfeld, although it applies to crisis management, provides a great way to self-audit: “There are known knowns: there are things we know we know. We also know there are known unknowns: That is to say, we know there are some things we do not know. But there are also unknown unknowns: the things we don't know we don't know". You can see a visual example of this in the Johari Window:

Source: Wikipedia

Here’s how you can take this approach and use it for yourself:

  • Identify your known unknowns: Skills you don’t currently possess that you’re able to recognize you need yourself.
  • Identify your unknown unknowns: Skills you don’t know you don’t currently have, but which your team can identify by asking them.

When it comes to projects, be inclusive

NASA astronaut Frank Borman, echoing a sentiment since shared by many people who’ve been to space, said: “When you're finally up on the moon, looking back at the earth, all these differences and nationalistic traits are pretty well going to blend and you're going to get a concept that maybe this is really one world and why the hell can't we learn to live together like decent people?”.

On an admittedly much smaller scale, the same learning can and should be applied to UX teams. When it comes time to take on a new project and define the vision, scope and strategy, bring in as many people as possible. The idea here isn’t to just tick an inclusivity box, but to deliver the best possible outcome.

Get input from stakeholders, designers, user researchers and developers. You certainly don’t have to take every suggestion, but a leader’s job is to assess every possible idea, question the what, why and how, and ultimately make a final decision. ‘Leader’ doesn’t necessarily have to mean ‘devil’s advocate’, either, but that’s another role you’ll also want to consider when taking suggestions from a large number of people.

Make time for your team

Anyone who’s ever stepped into a leadership role will understand the significant workload increase that comes along with it – not to mention the meetings that seemingly start to crop up like weeds. With such time pressures it can be easy to overlook things like regular one-on-ones, or at the very least making time for members to approach you with any issues.

Even with the associated pressures that come along with being a leader, stand-ups or other weekly meetings and one-on-ones should not be ignored.

Sit down with each member of your team individually to stay up to date on what they’re working on and to get a feel for their morale and motivation. What’s more, by simply setting some time aside to speak with someone individually, they’re more likely to speak about problems instead of bottling them away. Rotating through your team every fortnight will mean you have a clear understanding of where everyone is at.

Hosting larger stand-ups or weekly meetings, on the other hand, is useful in the way that large team meetings have always been useful. You can use the forum as a time for general status updates and to get new team members acclimated. If there’s one piece of advice we can add on here, it’s to have a clear agenda. Set the key things to cover in the meeting prior to everyone stepping into the room, otherwise you’re likely to see the meeting quickly get off track.

Keep a level head

You know the feeling. It’s Wednesday afternoon and one of the product teams has just dropped a significant amount of work on your team’s plate – a plate that’s already loaded up. While it can be tempting to join in with the bickering and complaining, it’s your job as the leader of your UX team to keep a level head and remain calm.

It’s basic psychology. The way you act and respond to different situations will have an impact of everyone around you – most importantly, your team. By keeping calm in every situation, your team will look to you for guidance in times of stress. There’s another benefit to keeping a level head: your own leaders are more likely to recognize you as a leader as well as someone who can handle difficult situations.

Two leadership development consultants ran a study of over 300,000 business leaders, and sorted the leadership skills they found most important for success into a numbered list. Unsurprisingly, an ability to motivate and inspire others was listed as the most important trait.

Be the voice for your team

While no user researcher or designer will doubt the value of UX research, it’s still an emerging industry. As a result, it can often be misunderstood. If you’re in charge of leading a UX team, it’s up to you to ensure that your team always has a seat at the table – you have to know when to speak up for yourself and your team.

If you a problem, you need to voice your concern. Of course, you need to be able to back up your arguments, but that’s the point of your role as a leader. Those new to leadership can find this aspect of the the job one of the hardest parts to master – it’s no surprise one of the key qualities in a great leader is an ability to speak up if they feel it’s the right thing to do.

Finally, you’ve got to assume the role of a buffer. This is another general leadership quality, and it’s similarly important. Take the flak from executives, upper management or the board of directors and defend your UX team, even if they’re not aware of it. If you need to take some information or feedback from these people and give it to your team, pay close attention to how you relay it to them. As an example, you want to be sure that a message about reducing customer churn is made relevant and actionable.

Master your own skill set

Stepping into a UX leadership position isn’t an excuse to stop developing yourself professionally. After all, it was those skills that got you there in the first place. Continue to focus on upskilling yourself, staying up to date on movements and trends in the industry and immersing yourself in the work your team carries out.

A leader with the skills to actually function as a member of their team is that much more capable – especially when another pair of hands can help to get a project over the line.

Wrap up

The field of user research continues to grow and mature, meaning the need for effective leaders is also increasing. This means there are near-limitless opportunities for those willing to step into UX leadership roles, provided they’re willing to put in the work and become capable leaders.

As we stated earlier, many of the skills that make a great leader also translate to UX leadership, and there’s really no shortage of resources available to provide guidance and support. In terms of UX specifically, here are a few of our favorite articles – from our blog and elsewhere:

min read
UX research is a team effort

What’s better than a UX team doing awesome research? A whole organization backing investment in UX research. What’s that look like in practice?  Collaboration and support from stakeholders across the organization throughout the research process from set up, doing studies, sharing insights, and digesting, understanding, and actioning recommendations based on the amazing insights you generate.

UX research should be something that is known, understood, and expected across your organization. Rather than keeping all the insight goodies to yourselves, why not democratize user research by making it accessible and shareable to all stakeholders to drive understanding of its value wherever they sit in the organization?

We go into this in more detail in our ebook UX Research for Teams. By including the stakeholders throughout the process, the role of research becomes a lot more visible throughout the organization. Having the best online tools to make the whole process simple and straightforward is a great place to start.

1. Who owns the research?

Recognition that the user research undertaken in your organization benefits the whole organization is essential for setting up key resources. By ensuring that everyone is operating from the same set of tools, the insights and results are easier to manage, find and file. It also means if someone leaves,  they don’t leave with all the insights and knowledge.

2. Everyone’s a researcher

Everyone within the organization should have the opportunity to be involved with UX research and should be encouraged to have a base understanding of the process (and even try out the tools) or, at the very least, have some understanding of the results and insights. If everyone has access to the tools, they can use these no matter where they sit in the organization. 

3. Don’t get distracted by shiny things

Maintaining a single source of research, with a well-organized filing system means you can always look at what has gone before. It is a great place to start. The best UX researchers often revisit past studies to see where to go from here. Creating consistency through the process and output means comparing insights are simpler.

4. Research is better with friends

What’s better than one mind? It’s two or more. Working alongside a team opens new perspectives, thinking, problem-solving, and approaches. New ways to see a problem and how to interpret insights and results. By socializing your results with the key stakeholders, you bring them on the journey, explaining how and why UX research is important to the project and the wider team. Firming up the opportunity for future research.

5. Qualitative research insights that are simple to find

Qualitative research tools are designed to assist you with testing types, including user interviews, contextual inquiries, and usability tests. Working as a team with tags, sorting, and recording can be made simple and streamlined. 

One of the best decisions you can make as a researcher is to bring the organization along for the ride. Setting up consistent tools across the team (and beyond) will help streamline research, making it simpler for all to be involved at each step of the process. Embedding UX research into each part of the organization. 

Take a look at our ebook UX Research for Teams, where we go into more detail.

min read
The Ultimate UX Research Repository: Empowering Your Entire Product Team with Specialized Tools

User research is vital to the product development process as it helps product teams understand their users' needs, behaviors, preferences, and pain points. By gathering insights from various research methods, such as user interviews, surveys, usability testing, and analytics data, product teams can make informed decisions based on evidence, rather than assumptions or personal opinions.

A UX research repository is a centralized database that stores all user research conducted by a product team, making it easily accessible and shareable across the entire team. There are many benefits to having a UX research repository, such as saving time and resources, enabling data-driven decision-making, and keeping everyone on the product team informed about user needs and preferences.

Specialized tools, like the Treejack tool, can make UX research easier, quicker, and more collaborative. In this article, we’ll discuss a bunch of tools and how they can (and should!) contribute to a centralized UX research repository.

Why a UX Research Repository is Necessary for Product Teams

A centralized UX research repository is a valuable asset for product teams to store and access research data related to user experience. It enables product managers and development teams to better understand their user's behavior, preferences, and expectations, which in turn enables them to make informed design and development decisions.

One of the key benefits of UX research repositories, like the Reframer tool, is that it saves time and resources. By storing user research data in one central location, teams can easily access and reuse existing research data. This saves them from having to conduct the same research repeatedly, which can be a waste of precious time and resources. Additionally, a centralized UX research repository can help teams to identify gaps in their research and prioritize areas for future research.

Another advantage of a UX research repository is that it facilitates collaboration across the entire team. With a central repository, research findings can be shared and discussed, enabling cross-functional collaboration. This promotes transparency and helps to ensure that everyone is working towards the same goals. It also helps to avoid duplication of effort, as team members can easily see what others have done, and what is still required.

Additionally, a UX research repository helps to ensure consistency in research practices. By defining research methodology, protocols, and use of prescribed specialized tools, product teams can collect data systematically and compare findings across different studies. This helps to ensure that the insights gained from user research are reliable and accurate, which in turn can be used to guide design decisions.

The Benefits of a UX Research Repository for Product Managers

A UX research repository helps product managers in several ways, including supporting informed product decisions, enhancing the user experience, and providing stakeholders with evidence-based research.

One of the significant advantages of a UX research repository is that it provides product managers with a wealth of data to make informed product decisions. Through usability testing, user interviews, and first-click testing (check out the Chalkmark tool), product managers can gain insights into how users interact with their products, what they like and dislike, and how they use them. By storing all this data in a central repository, product managers can quickly access all research data, not just their own, to inform their decisions about product development and design.

Another advantage of a UX research repository is that it helps to enhance user experience. Using video clips and other multimedia, product managers can share research findings with their team members and stakeholders, making it easier to understand user needs and preferences. This helps ensure that the product design is aligned with user needs, resulting in a better user experience.

Finally, a UX research repository provides stakeholders with evidence-based research to support product decisions. By presenting research findings to stakeholders, product managers can confidently stand behind future recommendations and iterations. This evidence-based approach helps to demonstrate that decisions are grounded in data and not just intuition or opinion.

The Role of Specialized Tools in UX Research

Specialized tools are essential for conducting high-quality UX research as they provide User Researchers with powerful data collection, analysis, and visualization features. These tools are particularly useful for conducting usability testing, user interviews, and surveys, as they help researchers to gather reliable and accurate data from users. Integrating these specialized tools into a UX research repository can help product teams to streamline their research process and facilitate collaboration within the team.

One such specialized tool is Treejack, which helps researchers to test the information architecture of a product or website. By using Treejack, researchers can review how users interact with navigation, site structure, and content, to ensure users can quickly and easily find the information they need. The results can then be stored in a UX research repository, allowing the team to access and analyze the data at any time.

Chalkmark is another tool that can enhance the quality of research by providing heatmaps and click-density grids of user interactions. These interactions can be tested on mockups and wireframes. Chalkmark helps researchers to identify where users are clicking and which areas are receiving the most attention, providing valuable insights for product design. By integrating Chalkmark into a UX research repository, product teams can store and access the data, making it easier to share insights and collaborate on product development.

Another useful tool is Reframer, which helps researchers to capture insights from user interviews and user testing sessions. Reframer enables researchers to record and transcribe interviews, tag key insights, and share findings with the team - acting as a functional research repository.

The Role of User Interviews and Usability Testing in UX Research

User interviews and usability testing are used in UX research to gather insights into user behavior, needs, and preferences. User interviews involve a one-on-one conversation between a User Researcher and a participant, where the researcher asks open-ended questions to understand the user's perspective. Usability testing, on the other hand, involves observing users as they interact with a product to identify usability issues.

Specialized tools play a crucial role in conducting user interviews and usability testing efficiently and effectively. These tools can help with data collection, organization, and analysis, making the research process more streamlined and insightful.

OptimalSort is a specialized tool that aids in conducting card sorting activities for usability testing. Card sorting involves asking users to organize concepts or items into categories to understand how they think about and categorize information. The OptimalSort tool enables researchers to conduct card sorting activities remotely and collect data on how participants group and label items. The tool also generates data visualizations and reports that can be added to the UX research repository for further analysis.

Optimal Workshop’s Reframer tool, mentioned earlier, has been designed specifically to enable researchers to capture and organize interview data in real-time. Researchers can tag and categorize interview data, making it easier to analyze and identify patterns across participants. It then stores this information in a centralized location for all research insights.  Reframer also generates reports and data visualizations, making data efficient to share and analyze across teams.

Conclusion

A UX research repository empowers entire teams to make informed product decisions, enhance user experiences, and provide stakeholders with evidence-based research. They can also support awareness and participation in UX among senior leaders, encouraging further research. 

Teams are increasingly using specialized tools like Treejack, Chalkmark, OptimalSort, and Reframer to conduct high-quality UX research as they provide powerful data collection, analysis, and visualization features. By using these tools together, product teams can streamline their research process and facilitate improved collaboration within the team. 

Are you interested in the benefits of a UX research repository? Check out how Optimal Workshop’s specialized research tools can add value to not only the quality of your data, but how your team collects, analyzes, and shares the results!

min read
Radical Collaboration: how teamwork really can make the dream work

Natalie and Lulu have forged a unique team culture that focuses on positive outputs (and outcomes) for their app’s growing user base. In doing so, they turned the traditional design approach on its head and created a dynamic and supportive team. 

Natalie, Director of Design at Hatch, and Lulu, UX Design Specialist, recently spoke at UX New Zealand, the leading UX and IA conference in New Zealand hosted by Optimal Workshop, on their concept of “radical collaboration”.

In their talk, Nat and Lulu share their experience of growing a small app into a big player in the finance sector, and their unique approach to teamwork and culture which helped achieve it.

Background on Natalie Ferguson and Lulu Pachuau

Over the last two decades, Lulu and Nat have delivered exceptional customer experiences for too many organizations to count. After Nat co-founded Hatch, she begged Lulu to join her on their audacious mission: To supercharge wealth building in NZ. Together, they created a design and product culture that inspired 180,000 Kiwi investors to join in just 4 years.

Contact Details:

Email: natalie@sixfold.co.nz

LinkedIn: https://www.linkedin.com/in/natalieferguson/ and https://www.linkedin.com/in/lulupach/

Radical Collaboration - How teamwork makes the dream work 💪💪💪

Nat and Lulu discuss how they nurtured a team culture of “radical collaboration” when growing the hugely popular app Hatch, based in New Zealand. Hatch allows everyday New Zealanders to quickly and easily trade in the U.S. share market. 

The beginning of the COVID pandemic spelled huge growth for Hatch and caused significant design challenges for the product. This growth meant that the app had to grow from a baby startup to one that could operate at scale - virtually overnight. 

In navigating this challenge, Nat and Lulu coined the term radical collaboration, which aims to “dismantle organizational walls and supercharge what teams achieve”. Radical collaboration has six key pillars, which they discuss alongside their experience at Hatch.

Pillar #1: When you live and breathe your North star

Listening to hundreds of their customers’ stories, combined with their own personal experiences with money, compelled Lulu and Nat to change how their users view money. And so, “Grow the wealth of New Zealanders” became a powerful mission statement, or North Star, for Hatch. The mission was to give people the confidence and the ability to live their own lives with financial freedom and control. Nat and Lulu express the importance of truly believing in the mission of your product, and how this can become a guiding light for any team. 

Pillar #2: When you trust each other so much, you’re happy to give up control

As Hatch grew rapidly, trusting each other became more and more important. Nat and Lulu state that sometimes you need to take a step back and stop fueling growth for growth’s sake. It was at this point that Nat asked Lulu to join the team, and Nat’s first request was for Lulu to be super critical about the product design to date - no feedback was out of bounds. Letting go, feeling uncomfortable, and trusting your team can be difficult, but sometimes it’s what you need in order to drag yourself out of status quo design. This resulted in a brief hiatus from frantic delivery to take stock and reprioritize what was important - something that can be difficult without heavy doses of trust!

Pillar #3: When everyone wears all the hats

During their journey, the team at Hatch heard lots of stories from their users. Many of these stories were heard during “Hatcheversery Calls”, where team members would call users on their sign-up anniversary to chat about their experience with the app. Some of these calls were inspiring, insightful, and heartwarming.

Everyone at Hatch made these calls – designers, writers, customer support, engineers, and even the CEO. Speaking to strangers in this way was a challenge for some, especially since it was common to field technical questions about the business. Nevertheless, asking staff to wear many hats like this turned the entire team into researchers and analysts. By forcing ourselves and our team outside of our comfort zone, we forced each other to see the whole picture of the business, not just our own little piece.

Pillar #4: When you do what’s right, not what’s glam

In an increasingly competitive industry, designers and developers are often tempted to consistently deliver new and exciting features. In response to rapid growth, rather than adding more features to the app, Lulu and Nat made a conscious effort to really listen to their customers to understand what problems they needed solving. 

As it turned out, filing overseas tax returns was a significant and common problem for their customers - it was difficult and expensive. So, the team at Hatch devised a tax solution. This solution was developed by the entire team, with almost no tax specialists involved until the very end! This process was far from glamorous and it often fell outside of standard job descriptions. However, the team eventually succeeded in simplifying a notoriously difficult process and saved their customers a massive headache.

Pillar #5: When you own the outcome, not your output.

Over time Hatch’s user base changed from being primarily confident, seasoned investors, to being first-time investors. This new user group was typically scared of investing and often felt that it was only a thing wealthy people did.

At this point, Hatch felt it was necessary to take a step back from delivering updates to take stock of their new position. This meant deeply understanding their customers’ journey from signing up, to making their first trade. Once this was intimately understood, the team delivered a comprehensive onboarding process which increased the sign-up conversion rate by 10%!

Pillar #6: When you’re relentlessly committed to making it work

Nat and Lulu describe a moment when Allbirds wanted to work with Hatch to allow ordinary New Zealanders to be involved in their IPO launch on the New York stock exchange. Again, this task faced numerous tax and trade law challenges, and offering the service seemed like yet another insurmountable task. The team at Hatch nearly gave up several times during this project, but everyone was determined to get this feature across the line – and they did. As a result, New Zealanders were some of the few regular investors from outside the U.S that were able to take part in Albirds IPO. 

Why it matters 💥

Over four years, Hatch grew to 180,000 users who collectively invested over $1bn. Nat and Lulu’s success underscores the critical role of teamwork and collaboration in achieving exceptional user experiences. Product teams should remember that in the rapidly evolving tech industry, it's not just about delivering the latest features; it's about fostering a positive and supportive team culture that buys into the bigger picture.

The Hatch team grew to be more than team members and technical experts. They grew in confidence and appreciated every moving part of the business. Product teams can draw inspiration from Hatch's journey, where designers, writers, engineers, and even the CEO actively engaged with users, challenged traditional design decisions, and prioritized solving actual user problems. This approach led to better, more user-centric outcomes and a deep understanding of the end-to-end user experience.

Most importantly, through the good times and tough, the team grew to trust each other. The mission weaved its way through each member of the team, which ultimately manifested in positive outcomes for the user and the business.

Nat and Lulu’s concept of radical collaboration led to several positive outcomes for Hatch:

  • It changed the way they did business. Information was no longer held in the minds of a few individuals – instead, it was shared. People were able to step into other people's roles seamlessly. 
  • Hatch achieved better results faster by focusing on the end-to-end experience of the app, rather than by adding successive features. 
  • The team became more nimble – potential design/development issues were anticipated earlier because everyone knew what the downstream impacts of a decision would be.

Over the next week, Lulu and Nat encourage designers and researchers to get outside of their comfort zone and:

  • Visit customer support team
  • Pick up the phone and call a customer
  • Challenge status quo design decisions. Ask, does this thing solve an end-user problem?

Seeing is believing

Dive into our platform, explore our tools, and discover how easy it can be to conduct effective UX research.