Venu Mathukumalli · designedbyvenu.com
Case study 05 Deep dive
A design-operations concept that connects people, projects, vendors, capacity and planning into one operating view for distributed design teams.
Real operational problem Self-initiated internal-tool concept / POC
00 At a glance
01 Operating problem
I managed full-time and contract design resources across multiple countries, vendors, time zones, projects, rates and renewal cycles. The information needed to run the team was fragmented, so every leadership question meant reconstructing the picture from scattered tools.
The real problemThere was no single operating view of the design organization.
The core question
How do you turn fragmented team, vendor, project and budget information into one operating system for design leadership?
Thesis A design team should be managed from one operational view, not reconstructed from scattered tools every time a leader asks a question.
My role
I defined the product concept from problems I encountered while managing a distributed design organization. I mapped the information leaders repeatedly needed, organized it into an operating model, designed the workflows and dashboards, and built the concept prototype.
Self-initiated internal-tool concept / POC. It was inspired by my real design-management responsibilities and operating pain, but it was not a formally deployed enterprise system. Every person, vendor, project, date and cost shown here is invented.
02 What I needed to manage
Every staffing or budget question touched several of these at once:
Who it is for
Roles, not personas: these were never validated as research personas.
Primary
Secondary and read-only
03 Product model
People → Vendors → Projects → Capacity → Spend → Performance → Planning. The system map shows what the product holds; the workflow shows how a leader moves through it.
One operating viewEvery part answers its question in relation to the others.
The workflow
Plan → Staff → Assign → Monitor → Review → Renew.
Renew feeds the next Plan: the workflow is a loop, not a checklist.
04 Information architecture
Product areas, not navigation labels: each one is a different lens on the same connected records.
05 Key design decisions
The value is not a prettier roster. The value is in connecting the records a leader otherwise reconciles by hand.
What I stopped designing
What I designed instead
06 Team, vendor & project workflows
People-centered operations and collaborative planning, not HR software. Each screen is recreated as concept UI with invented people, vendors, projects, dates and costs.
07 Prototype
The earlier working prototype is private. It was built as a concept prototype on real organizational information, so it is not shown or linked here. The screens on this page recreate its important views with invented people, vendors, projects, dates and costs.
08 Outcome
No metrics are claimed.
Reflection
Design operations is not a collection of administrative tasks. It is a connected system of people, capacity, projects, vendors and decisions.
The most useful insight was seeing those relationships. Once they became visible, the product structure became much clearer.
I’m happy to walk through this project, the decisions behind it and what I’d do next, in more detail.