Asha

Plan and manage work using KPIs and OKRs

about

About the project

Asha is an all-in-one B2B platform designed for ambitious organizations to align their workforce. It serves as a bridge between high-level strategy (OKRs/KPIs) and professional development, i.e., project and task-based learning. It ensures that organizational values, metrics, OKRs, and more are properly structured, aligned, and communicated.

Project Goal

The primary goal was to design a unified platform that visualizes the direct relationship between high-level company OKRs & KPIs and how deliverables, and tasks move the needle on a global objective.

My Role

UX Researcher

UI / UX Designer

My Responsibilities

Research
UI / UX Design
Interactive Prototyping

The Problem

Modern teams are forced to perform manual data syncing across different platforms if any. They track OKRs in one app, KPIs in a spreadsheet, and Project, Tasks in a third tool.

Design Objective

Create a unified platform where teams can plan work, track progress, connect learning to work, and measure impact,
with an intuitive, engaging experience that supports visibility and alignment.

The Value Proposal

Asha empowers teams to:

Align daily work with company-wide objectives in real time
Track performance through clear, visual progress indicators
Integrate learning directly into work execution
Improve decision-making through transparent goal visibility

screens

Screens

Create & Assign Deliverable

The Create and Assign Deliverables feature enables teams to define, structure, and delegate measurable work outputs within Asha. It ensures that strategic objectives are translated into clearly defined deliverables that are assigned to the right teams, tracked over time, and validated with proof of completion.

This feature sits at the core of Asha’s performance execution system, bridging planning, accountability, and reporting in a single workflow.

Value delivered:

Standardise how work outputs are defined and tracked
Improve ownership clarity across teams
Strengthen accountability through evidence-based completion
Bridge the gap between strategic planning and execution

View Deliverable - Kanban Vs List view

Kanban view:
Emphasizes visual workflow stages, progression, and task-level granularity.

Status Columns: Deliverables are organised into three clear operational columns: To Do, In Progress, and Completed.
Granular Task Inspection: Users can expand individual deliverable cards to view, check off, or add sub-tasks directly from the board view e.g. expanding the "Well designed sales process map." card reveals its individual sub-tasks and specific due dates.
Progress Visuals: Dynamic progress bars (e.g. 50% or 70%) and explicit status tags such as Overdue offer immediate visual indicators of project health.

Index view:
Provides a clean, condensed, and highly scannable spreadsheet-like layout optimized for rapid status auditing.

Categorized Rows: Deliverables are grouped sequentially under text-based section headers: To Do , In progress , and Completed.
Data Density: Each row standardizes key metadata into discrete columns for quick reading: Deliverable Name, Progress Bar, Collaborators (via avatars), and Due Date/Status (e.g. Today, Sep 30th, Overdue, Completed).
Clean Hierarchy: Sub-tasks are collapsed by default under a dropdown, keeping the interface uncluttered while allowing users to drill down when necessary.

View Deliverable details

The details view provides a centralised, 360 degree overview of a specific strategic deliverable e.g. Customer Behaviour Analysis Report. It connects execution-level tasks with top-level organisational strategy, ensuring accountability, alignment, and clear tracking of progress.

1. High-Level Metrics & Progress Tracking
At the top, users get an immediate snapshot of the deliverable's current health and completion status including; overall progress, evidence of done,

2. Strategic Alignment & Metadata:
This section breaks down why the work is being done and who is responsible for it, establishing a clear line of sight across the organisation:

3. Task Management:
The bottom of the main panel acts as the engine for execution, listing the specific operational steps required to complete the deliverable i,e a well structured task list with an ability to add tasks inline without leaving the page.

4. Engagement & Collaboration Panel:
A dedicated, tabbed sidebar streamlines team communication and historical auditing without cluttering the main workspace i.e an audit log of all updates made to the deliverable, including objective updates, Key Result changes, task additions or changes and direct mentions.

Key Takeaways

The Asha platform was able to lead to:
1. Unified visibility, driving cross-functional transparency

2. Tight OKR alignment preventing feature creep by explicitly mapping each deliverable to a particular Objective

3. Clear ownership reducing execution gaps