
Timeline
8 weeks
Platform
Internal enterprise tool
This project focused on designing an internal Portfolio Management Tool used by teams responsible for planning, tracking, and evaluating multiple initiatives at once.
The existing workflows relied on a mix of spreadsheets, static dashboards, and manual reporting. While data was available, it was scattered across tools, making it difficult to maintain a shared understanding of portfolio health and priorities.
The goal was to bring clarity, structure, and confidence into how teams viewed and managed their portfolios.
Users
Decision-makers / Leaders
Project & Portfolio Managers
Cross-functional Stakeholders
Every user group had unique requirements, yet they all shared a fundamental question: “How can I bring this together?”
Why This Mattered
Managing multiple initiatives isn’t just about tracking numbers—it’s about making the right decisions at the right time.
Without a clear, unified view:
• Prioritization discussions became subjective
• Important signals were buried in data
• Decision-making slowed due to lack of shared context
By designing a tool that surfaced what mattered most, preserved context, and supported comparison, the experience helped teams move from reactive reporting to confident decision-making.
In a high-stakes environment, clarity isn’t a nice-to-have—it’s essential.
Research & Key Insights
During stakeholder discussions, I observed challenges in gathering team updates and accessing quick, high-level insights. This led to proposing a centralized portfolio-level platform to project managers, which was approved by leadership. The following insights emerged from subsequent research.
Key Insights
01
Progress updates lived across spreadsheets, dashboards, slide decks, and meetings, forcing users to mentally stitch information together.
02
Users hesitated to act on insights because actual results were difficult to validate against targets due to disconnected systems and delayed updates.
03
Cost savings, time savings, and project impact existed but were buried across systems, making it hard to communicate value.
04
Without automation or notifications, users relied on frequent manual checks to stay updated.
My Role
Project Lead & UX Designer
8 Weeks
Internal enterprise tool
Framing the problem with stakeholders
Identifying user pain points across the workflow
Defining clearer user flows
Designing wireframes and interaction patterns
Iterating based on feedback and usability insights
The Problem
Teams managing multiple initiatives struggled to maintain visibility, prioritization, and confidence across portfolios. Information was fragmented across tools, making it difficult to assess performance, compare initiatives, and make timely decisions.
Key Pain Points:
Solution Strategy
I focused on designing a product that not only supports leadership team but also project managers and stakeholders
Design Principles
User Flow
The UX “Aha” Moment
The key “aha” moment came when users saw portfolio-level insights consolidated into a single, reliable view—eliminating tool-hopping and enabling confident decision-making
Impact & Outcome
Due to confidentiality, impact was measured qualitatively and through feedback—but the improvements were clear.
Observed Outcomes
Leadership gained quick, high-level visibility across projects, enabling confident presentations without additional preparation
Project managers could easily track planned versus actual performance across projects in a single tool.
Automation and notifications enabled timely updates, reducing the need for manual follow-ups from leadership
By becoming a centralized workspace, the tool significantly increased adoption and reduced task effort
The solution transformed a fragmented, time-consuming workflow into a centralized, trusted system—improving adoption, reducing manual effort, and enabling confident, timely decision-making across teams.
Reflection & Learnings
What this project reinforced for me
This project strengthened my approach to designing enterprise experiences that prioritize clarity, trust, and decision-making over surface-level complexity.
Confidentiality Note
This case study is a reimagined version of real-world work. All names, visuals, and data have been anonymised to respect confidentiality.





