top of page

Create

Tools and Methods

Service Blueprints

Jira 

Confluence

Length of phase

4 months

# participants

30+ users

Create Overview

Next, we brought ideas to life. Starting with low-fidelity prototypes, we visualized the new onboarding process using simple tools and existing Jira structures. These prototypes were refined into high-fidelity models that incorporated real data, automations, and detailed task breakdowns. By testing these prototypes with stakeholders, we ensured the solution met user needs and expectations.

Screenshot 2024-12-12 at 1.32.18 PM.png

High-Fi Prototype

The higher-fidelity prototype was then presented to all stakeholders and end users to assess whether the solution remained viable and aligned with customer needs. Fortunately, it received approval, allowing us to take the prototype to the next level. We enhanced it by adding more information, updating texts, incorporating materials, defining responsibilities, implementing automations, and integrating necessary artifacts. These improvements paved the way for the creation of our Minimum Viable Product (MVP), bringing us one step closer to the final, fully functional onboarding process.

IMG_3782.jpg

Outcomes

​

  • Delivered functional prototypes demonstrating the unified onboarding structure.

  • Stakeholder alignment and approval of the new process.

  • Refined and validated workflows ready for phased implementation.

Low-Fi Prototype

After gathering feedback from our multidisciplinary team and securing approval from the customer —confirming that the proposed solution indeed met their needs—we progressed to creating a higher-fidelity prototype. This next step allowed us to refine and detail the solution further, incorporating the insights and adjustments from the initial testing phase to ensure that the final product would be both functional and user-friendly.

Screenshot 2024-12-12 at 1.34.08 PM.png

Develop new onboarding materials

To further our understanding, we engaged with several users to identify all parties involved in the project. Visualizing these stakeholders in a single map helped us understand their interactions with the customer and with each other. Stakeholder maps are beneficial as they provide a clear overview of all parties involved, their relationships, and their roles in the project. This visualization aids in identifying key influencers, decision-makers, and collaborators, ensuring a more comprehensive approach to service design.

Previous

Next

bottom of page