CognitiveBotics: Plan and Track
Simplifying clinical workflows for therapists supporting children with autism and other learning disabilities. What began as a visual redesign evolved into a complete rethink of the product's structure and workflows.
Role
Product designer
Team
2 designers, Product team, Engineering team, 1 BCBA
Timeline
Sept 2025 - Sept 2026
Skills
Information architecture, Interaction design, Design systems
At a glance
Responsive by necessity
Most centers in India work on phones and tablets - so every flow was designed for small screens alongside desktop.
Therapist platform
Redesigned core workflows spanning onboarding, care planning, sessions, reporting, and adaptive recommendations.
Cross-platform design system
Built alongside the product and adopted across multiple web and mobile experiences.
CONTEXT
The workflow was familiar, but getting around it wasn't
Plan and Track already supported the therapist’s workflow, but years of features being added on had made the product harder to navigate. Related information lived in different places, and many day-to-day processes were still happening on paper.
I expected to update the interface to reflect the new brand. That turned out to be the smallest problem. The bigger opportunity was restructuring the product around how therapists actually worked, without disrupting a workflow they already understood.
How might we organise the platform around how therapists work, rather than around a list of features?
DECISION MAKING
One clinical expert, lots of unanswered questions
We had a BCBA on the team who worked directly with therapists and children, so I could check decisions with someone who knew the clinical workflow. I also worked closely with the senior designer who built the first version and understood why earlier decisions had been made.
Direct access to specialist therapists across India was limited, so not every decision could be validated before shipping. When we had to make a call, I kept coming back to three principles:
Reduce cognitive load
Help therapists focus on the task, not navigating the software
Support clinical judgement
Provide guidance without making decisions on the therapist’s behalf
Think beyond the screen
Design around what brought therapists here and what they need to do next
WHERE WE STARTED
450+ objectives
1 learning plan
We started with Child Onboarding because almost every other workflow depended on it. Assessments, learning plans, recommendations, sessions, and reports all stem from decisions made here.
The original experience put everything on a single screen and relied on therapists already knowing what came next. That might work for experienced users, but we were also designing for centres in India where therapists often had varying levels of experience and needed more support from the product itself. We reorganised the flow around the order those decisions naturally happen. The decisions didn’t get simpler. They just stopped arriving all at once.
Enter details
Build plan
Preview and confirm
INFORMATION ARCHITECTURE
Helping the therapist get to where they want to go
Once Child Onboarding was working, we applied the same thinking across the rest of the platform.
Therapists don't think, "I need to go to Reports." They're thinking, "I need to prepare for Aarav's session." We reorganised the experience around that workflow.
Hunting for information in several places → One clear next step in one place
Deciding what not to show
The previous dashboard gave therapists a snapshot of the platform: charts, counts, appointments, and activity. Some of the information was useful, but it didn't answer the one question therapists asked when they logged in:
“What do I need to work on today?”
The redesign shifted the dashboard from monitoring the platform to supporting the therapist's workflow. Instead of asking therapists to open each child's profile to understand what had changed, we surfaced the information that required action directly on the dashboard.
Children who were progressing normally became much quieter in the interface, making it easier to focus on the work that actually required attention.
Old platform dashboard
Revamped dashboard
CHANGING COURSE
A decision I reversed
Early in the project, we wireframed the Content Library as its own destination, where therapists would browse skills and drill into objectives across multiple pages. By the time we built it, the rest of the platform had evolved. We had established reusable components, clearer navigation patterns, and a better understanding of how therapists worked.
Instead of following the original wireframe, we rebuilt the experience around patterns therapists already knew. Skills, objectives, and details came together in one searchable workflow, making it faster for therapists to navigate and simpler for engineering to build.
Original wireframe
What we built instead
scaling
Owning the product beyond the redesign
After the redesign shipped, I became the main designer for new features. Over time, we extended the platform using the workflows and components we had already established.
Adaptive suggestions
AI-driven changes and recommendations that support clinical judgment
Notifications
Bring important updates to therapists instead of making them search
History & audit log
Make changes traceable without cluttering everyday workflows
Desktop → mobile sessions
Transition from planning to therapy without losing context
Download detailed reports
Dense clinical data designed to be scanned quickly
Platform swap
Helping users adopt the new experience
OUTCOMES
Where we are now
Everything has shipped, but it’s still too early for usage numbers I’d consider meaningful. These are the outcomes we’ve already seen internally.
A product therapists can learn
The platform now supports therapists through consistent workflows instead of relying on prior product knowledge.
Built to evolve
Established patterns helped design and engineering ship new features without rebuilding workflows from scratch.
Faster product delivery
Shared components, interaction patterns, and clearer workflows reduced design and engineering effort as the platform continued to grow.
REFLECTION
What I’d do differently
Cleaner ≠ better
Reducing clutter improved usability, but early feedback from therapists in India showed that clarity alone could still feel visually flat. I’d balance simplicity with more warmth and personality.
Validation before UI
I’d spend more time testing the structure, terminology, and onboarding across different centres before refining the interface.
Don’t start with the screen
I now spend more time understanding what happens before and after a screen before deciding what belongs on it.