APP_Mockup.jpg

Communication APP

A new app that improves communication.

* Project details are hidden due to privacy.

 
 

It All Started With a Vision

Our strategy team was in charge of creating a communication solution that could become a game-changing product for our company. It was an exciting opportunity, but it wasn’t without its challenges. The question was straightforward: How could we create something truly innovative that aligned with user needs, technical feasibility, and the company’s business goals?

The journey began with a Proof of Concept (PoC). While our initial ideas seemed promising, rigorous testing revealed gaps in the solution. User expectations didn’t fully align with our envisioned features, and stakeholder priorities frequently shifted. The challenge was to bring clarity and structure to the chaos while keeping the vision intact. Eventually, the PoC secured approval to move to production through persistence and collaboration.

But this was just the beginning.


Creating Roadmaps: From Chaos to Clarity

As the sole UX Designer and Strategist, I knew the success of this project depended on creating a clear, actionable roadmap. Starting from scratch, I meticulously mapped out the entire process, including defining Epics and crafting User Stories to break down complex tasks into manageable pieces.

This involved:

  • Defining requirements in the form of Epics and Stories.

  • Managing the backlog and structuring the iteration planning process.

  • Leading the product release planning, setting expectations, and creating a phased approach to delivery.

Key challenge: I had to wear many hats with no team to split responsibilities. I balanced strategic planning with tactical execution, keeping stakeholders informed and developers aligned while staying on top of every detail.

Outcome: A detailed roadmap that served as the foundation for structured, efficient collaboration across all project phases.

An example of one of the main features Road Map.

Feature Mapping: Designing for Impact

With the roadmap in place, I dived into feature mapping to identify and prioritize the product's most impactful components. This step required deep user empathy, strategic planning, and technical awareness to ensure the design was innovative and feasible.

  • The challenge was balancing user needs with technical constraints. For example, users demanded seamless real-time updates and integration with existing systems, features that required creative solutions to fit within tight timelines.

  • My approach: I worked closely with developers and stakeholders to simplify complex functionalities while preserving an intuitive and satisfying user experience.

Outcome: A prioritized, user-centric feature map that served as the backbone of the design process.

User Stories definition for this Epic

Wireframing: Bridging Ideas and Execution

With no team to collaborate with, I owned wireframing to visualize and iterate on design concepts. This phrase became essential for aligning expectations and providing clarity across all teams.

I created detailed wireframes that:

  • Addressed both big-picture user flows and granular details like mobile responsiveness.

  • Helped developers visualize the product early, reducing miscommunication and rework.

  • Allowed stakeholders to see progress and provide meaningful feedback.

Key challenge: As the sole designer, I managed misaligned expectations across multiple teams while maintaining momentum. Regular design reviews and feedback sessions were critical to ensuring alignment.

Wireframing

Specifications: The Blueprint for Success

I created a Functional and Technical Specification document in Confluence to ensure a seamless transition from design to development. This document became the team's single source of truth.

The document included:

  • Product structure and detailed design archives.

  • Variations and guidelines for mobile behaviour.

  • Comprehensive front-end and back-end acceptance criteria.

  • Clear and actionable user stories.

Key challenge: The feature set constantly changed, so the specifications had to remain up-to-date and accessible. I ensured this by communicating closely with developers and updating documentation in real-time.

Outcome: A robust, well-documented guide empowered teams to deliver the product confidently.