Designing and communicating a design methodology that actively involves every team member to enhance success and foster a shared understanding.
How can we effectively align the vision and understanding of a problem among business, tech, and design stakeholders?
What was deliver and how
Workshop
Wireframe mapping
Deliverable orgaisation
OOUX technique
Wire framing
Rolling out the 'History Feed' feature was a real game-changer for us. It made life so much easier for our brokers by centralizing all client interactions. Testing became a breeze with those simpler tickets, and design tweaks were a snap thanks to the ORCA technique. And you know what? Users loved it! Overall, it was a big win for everyone involved.
The challenge lies in harmonizing the perspectives of business, user, and tech stakeholders regarding the feature's design and functionality.
From my past experience, I've learned the importance of involving all stakeholders early on to avoid misunderstandings. Previously, working in isolation led to prototypes being altered beyond recognition during implementation, making it difficult to verify usability. By collaborating from the start, we can ensure that the end product remains user-friendly and aligned with both business goals and technical capabilities..
Currently, essential interactions, like customer care calls or comments, are scattered across multiple platforms, hindering efficient access and utilization of crucial information.
To improve client interaction and service personalization, there's a pressing need to centralize these records into a unified 'History Feed,' enabling brokers to access comprehensive interaction histories effortlessly.
A dedicated section within the application card specifically designed to reference interactions between clients and the company.
This approach effectively centralizes communication records, providing brokers with easy access to comprehensive interaction histories.
Having a meeting with Product Manager, Deigner and Enginering manager helped us unsuring clarity on the objectives, constraints, and desired outcomes of the feature
As the backend was already existing, the first step of the conversation was agreeing on what could be shown to the user from a technical perspective.
To ensure alignment and agreement on the desired outcome, we employed a visual aid: the ORCA technique. This technique allowed us to effectively visualize the applicant card with the new feature, ensuring a shared understanding among all stakeholders.
The ORCA technique, short for Objectives, Roles, Controls, and Actions, is a visual communication tool used to clarify and align stakeholders' understanding of a project or feature
After collaborating with stakeholders, I conducted a reflection on the implications of the new structure on user navigation. It became evident that proceeding with this decision would result in an exhaustive applicant card.
Therefore, I undertook a revision of the structure and subsequently shared it in another meeting with the product and engineering managers.
Thanks to the ORCA technique, we can quickly validate the structure and progress with the design
Since we have previously built a history feed for the Potential Buyer card, I will reuse components from that section. This section has undergone testing and iteration with users.
.png)
.png)
Therefore, the product manager, engineering team, and design team have collectively decided that we can release the feature with confidence, particularly considering the success of a similar feature in our internal tool.
The delivery process is streamlined by breaking down large features into smaller, more manageable tickets. In our team, lacking a QA department, it's crucial to have clear tickets for testing and ensure swift delivery during sprints. Consequently, we consistently seek opportunities to divide tickets into smaller units.
As a designer, I always proactively assess whether the design can be deconstructed and completed in phases
.png)
.png)
Because status updates and meetings originate from different data sources, their delivery will be delayed until we have the necessary backend tickets. Additionally, I have made the decision to separate the comment action as its own ticket.
In summary, the design has been deconstructed into three tickets, enabling faster delivery, improved testing, and optimal sprint performance
.png)
By using a ticket-based approach, the team balanced speedy delivery with the ability to adapt to changes. While they began with a complex solution, breaking it down into smaller tickets made the development process smoother, leading to a strong and easy-to-use feature.
With our team of four engineers and one engineering manager, we experienced a significant boost in sprint productivity. Transitioning from completing 100 story points per sprint to achieving 150 story points highlights the enhanced efficiency and delivery speed we achieved.
The implementation of smaller, more manageable tickets resulted in a streamlined testing process. With simplified tickets, testing became faster and more accessible to all team members. This led to quicker identification and resolution of issues, ensuring a smoother development cycle.
The integration of the ORCA technique into our design process revolutionized our iteration speed. By visualizing project objectives, roles, controls, and actions, we expedited decision-making and prototyping. This allowed us to iterate rapidly without compromising on design quality, ultimately saving valuable time and resources.
In wrapping up, our project journey shows the power of teamwork and flexibility. With a ticket-centered approach, we boosted sprint efficiency, simplified testing, and sped up design. These wins highlight the importance of staying adaptable and striving for improvement. Looking ahead, we'll keep applying these lessons to craft better user experiences and deliver solutions that truly hit the mark.
