How deep user research, deliberate design trade-offs, and an ambient AI strategy shaped an enterprise platform that transforms resource allocation from spreadsheet chaos into confident, data-driven decisions. Product details abstracted for stealth.
CIOptimize is an AI-driven resource allocation and project portfolio management platform built for professional services firms. When I joined as UX Lead, the product was a data-display tool — it showed allocation tables but never surfaced decisions. My mandate: reimagine the platform as a decision-confidence system where AI, interaction design, and information architecture work together to help managers allocate the right people to the right projects at the right time.
This case study documents the design thinking, user research, strategic trade-offs, and interaction design decisions that shaped the platform. Because CIOptimize is in stealth mode, I focus on rationale and methodology rather than production UI.
Professional services — consulting, IT services, engineering, architecture — is an industry where revenue is people. Every dollar of revenue traces back to someone being allocated to the right project, at the right time, with the right utilization. Unlike manufacturing or SaaS, there’s no inventory buffer. An unallocated consultant is pure revenue loss. An overallocated one burns out, delivers poorly, and churns.
And yet, this $2.3 trillion global industry makes these high-stakes decisions using the same tool it used in 1995: spreadsheets. Not because firms haven’t tried software — they have. The tools just never worked. They were either too rigid (built for manufacturing resource planning), too shallow (pretty calendars with no intelligence), or too disconnected (analytics in one silo, scheduling in another).
CIOptimize was built because the gap between what exists and what’s needed has never been wider — and because the emergence of practical AI finally makes the vision achievable.
Spreadsheets can store allocation data, but they can’t think about it. They can’t tell you that moving Sharma to Project Atlas in Week 16 will overallocate her by 0.3 FTE and create a cascading conflict with Horizon. They can’t tell you that Müller has a bench window opening in Week 18 that perfectly matches incoming demand. Every “what if” requires a human to manually trace dependencies across tabs, rows, and mental models. This is the ceiling that no amount of Excel wizardry can break through.
We studied why previous tools failed. Legacy PSA platforms were designed for billing, not decision-making — they captured time after it was spent, not before it was planned. Modern PM tools made beautiful timelines but had no concept of FTE intensity or overallocation. BI platforms offered analytics but were disconnected from the workflow where decisions actually happen. Each tool solved one piece while ignoring the system. CIOptimize was built to be the system — where planning, intelligence, and action live in a single surface.
This product couldn’t have existed three years ago. The vision requires AI that generates contextual, trustworthy narrative summaries about resource allocation patterns — not just dashboards, but natural-language insights like “Sharma is overallocated across two Transform projects; recommend shifting 0.3 FTE from Atlas.” Previous-generation ML could detect anomalies; today’s AI can explain them, contextualize them, and suggest specific actions. This inflection made the “decision confidence system” vision achievable for the first time.
Every feature in CIOptimize maps back to a specific failure in the status quo. This isn’t technology looking for a problem — it’s observed pain driving every design decision.
Three forces converging at the same moment made this the right time to build CIOptimize.
Large language models can now generate contextual narrative summaries of allocation data — not just charts, but explanations with specific, actionable recommendations. Previous-generation analytics could show a red dot; modern AI can tell you why it’s red and what to do about it.
Post-pandemic professional services firms face compressed margins and talent scarcity. The cost of misallocation — bench time, burnout, project delays — has never been higher. Firms that previously tolerated spreadsheet inefficiency now face existential pressure to optimize their people deployment.
Remote and hybrid work shattered the hallway-conversation staffing model. When managers could see their team in the office, tribal knowledge worked (barely). With distributed teams across time zones, the information asymmetry became untenable — you can’t manage what you can’t see.
A generation of managers raised on consumer-grade software expects real-time, scannable, intelligent interfaces — not the clunky enterprise tools of the 2010s. The bar for enterprise UX has risen dramatically, and legacy PSA tools feel like time travel in the wrong direction.
Not a better spreadsheet. Not a prettier calendar. A decision-confidence system where managers feel they already know the right answer — because the interface surfaced it before they had to go looking.
Professional services — consulting, IT services, engineering — is a $2.3 trillion global industry where revenue is directly tied to how effectively firms deploy their people. Yet most firms manage this with fragmented spreadsheets, tribal knowledge, and reactive decision-making.
Through stakeholder interviews, contextual inquiry, and workflow observation, I mapped three systemic failures that cascade from the spreadsheet problem into real business pain.
Capacity data lived in disconnected spreadsheets across teams. No one had a real-time view of who was available, overbooked, or approaching bench time. Staffing decisions were made with 3-5 day old data — an eternity in a fast-moving consulting firm.
A single allocation change triggered 4-7 emails, 2-3 Slack threads, and at least one meeting. Cloning a project structure took a full day of manual data entry. Resource managers spent 70% of their time on logistics, not judgment.
Tools showed data but never insight. No way to see if an allocation change would create downstream conflicts. No scores for project health or resource alignment. Every decision was made blind, then corrected retroactively.
Research combined 12 stakeholder interviews, contextual inquiry sessions (observing managers doing allocation planning live), workflow mapping, and quantitative audit of existing data patterns. Here are the critical findings that shaped every design decision downstream.
Research revealed three distinct user archetypes operating at different decision altitudes. Each asks fundamentally different questions, works at different time horizons, and needs different levels of data granularity. The IA must serve all three without forcing any to wade through irrelevant information.
Through contextual inquiry, I mapped the end-to-end resource allocation journey as experienced by the Resource Orchestrator persona. The journey revealed that the biggest time sink isn’t making decisions — it’s gathering the context to make them.
I audited seven competing platforms across five dimensions that matter most to our personas. The analysis revealed a clear market gap: no tool combines enterprise-grade allocation management with embedded AI intelligence. Competitors either do scheduling well or analytics well — never both in the same workflow.
| Capability | Legacy PSA Tools | Modern PM Tools | BI / Analytics | CIOptimize Approach |
|---|---|---|---|---|
| Real-time capacity view | Delayed sync | Yes | External data | Live heat-map grid |
| Conflict detection | Manual review | Basic warnings | Not applicable | Inline per-cell alerts |
| AI-generated insights | None | None | Separate dashboards | Ambient inline |
| Change audit trail | Basic log | None | None | Saveable filter views |
| Portfolio health scoring | None | Project only | Custom dashboards | Multi-dimensional scores |
| Clone/template workflows | Basic copy | Templates | None | Split-panel wizard |
| Progressive disclosure IA | Flat navigation | Role-based access | Dashboard-centric | 3-layer drill-down |
Rather than a waterfall approach, the design process was structured as a 26-day intensive sprint with four overlapping phases. Each phase produced concrete deliverables that were immediately testable with stakeholders. The key methodological choice: high-fidelity HTML prototypes from day one, not wireframes.
Why skip wireframes? In enterprise data-dense products, the difference between wireframe and production is where all the design decisions live — column widths, cell padding, color encoding thresholds, typography hierarchy in a 200-cell grid. Low-fidelity artifacts couldn’t carry this information.
Conducted 12 stakeholder interviews across three persona types. Ran contextual inquiry sessions observing resource managers doing live allocation planning. Mapped the four-stage workflow, identified the 70% conflict-detection bottleneck, and documented 47 discrete pain points that were synthesized into 8 opportunity areas.
Designed the three-layer progressive disclosure IA (Strategic / Operational / Individual). Defined the ambient intelligence approach — AI surfaces in-context, never behind a chatbot or separate tab. Established the “decision-confidence system” framing that became the product’s north star. Created the initial scoring model framework (engagement, alignment, health).
Built self-contained HTML prototypes for each major feature surface: heat-map allocation grid, AI summary panel, clone project wizard, change log, score cards, and capacity charts. Each prototype was pixel-precise to the production design system. Iterated through 3–5 rounds of screenshot-driven feedback per feature, progressively refining toward restrained density aesthetics.
Ran validation sessions with all three persona types using interactive prototypes. Documented 23 interaction patterns and 6 reusable component specifications. Created a comprehensive design process document for the internal team. Established the prototype-to-production iteration workflow that continues to accelerate feature delivery.
The IA’s core principle: each layer answers a different question at a different altitude. Users navigate between layers through contextual drill-down — clicking a project score in the portfolio dashboard takes you to that project’s team allocations, which lets you drill into an individual resource’s schedule. The system always preserves breadcrumb context so users know where they came from.
Smart defaults by role: executives land on Layer 1, resource managers on Layer 2, individual contributors on Layer 3 — but everyone can navigate up or down. Access adapts without restricting.
Every product is defined by the decisions that weren’t obvious. This section documents the pivotal design choices — what alternatives were explored, why they were rejected, and the reasoning that led to each commitment. These are the moments that defined the platform’s UX identity.
Through iterative prototyping, six core interaction patterns crystallized. Each pattern was designed once, documented, and reused across multiple features — ensuring consistency while accelerating development velocity. These patterns are the building blocks of every view in the platform.
While CIOptimize remains in stealth, these representative screens illustrate the design system in context — how patterns, color semantics, and information hierarchy come together in production views. Specific data is fictional; layout, density, and interaction patterns are accurate to the shipped product.
Product-level decisions set direction. Component-level decisions determine whether the product actually feels right in use. This section documents the granular UI choices behind individual elements — the decisions that live below the surface but shape every interaction.
The design system was built iteratively through prototyping rather than designed upfront. Each prototype round revealed which tokens, components, and patterns needed to be systematized. The result is a tight, opinionated system that enforces the “restrained density” principle — preventing visual noise as features expand.
Colors carry meaning, not decoration. Every color maps to a data state.
The AI strategy was the most consequential design decision in the product. Rather than building “AI features,” we embedded intelligence into the fabric of every existing view. The key philosophical shift: AI should feel like better data, not a separate tool.
This section documents the three pillars of the AI UX strategy, each addressing a different aspect of how intelligence appears, how users trust it, and how it earns adoption without forcing behavior change.
AI summaries, scores, and recommendations appear inside the views where decisions happen, not behind a chatbot or separate tab. The AI summary panel sits alongside the allocation grid. Score chips appear in resource cards. Conflict warnings show inline in the clone wizard. Users encounter intelligence at the moment of decision, not as a separate workflow step.
Every AI-generated element shows its provenance and freshness. The five-state freshness machine (fresh / stale / never-generated / in-progress / just-refreshed) ensures users always know when data was computed. Stale states include a one-click refresh CTA. Just-refreshed states highlight what changed. Users trust intelligence they can interrogate.
AI never commits changes autonomously. It surfaces recommendations (“consider shifting 0.3 FTE from Atlas”), detects conflicts (“2 overallocations in W16–17”), and predicts impact (“bench window opens in W19”) — but the human always makes the final call. Trust is earned incrementally; automation can expand as confidence grows.
Every design system makes bets about fundamental tensions. These are the positions CIOptimize deliberately chose — and the reasoning behind each. The marker position represents our current bet; the context explains why.
These six principles were distilled from research insights and design decisions. They serve as a shared language for the team — when evaluating any new feature or design, we ask: “Does this uphold the principles?”
Every view answers “what should I do next?” not “here is data.” Surfaces actions and recommendations, not raw information.
Three layers of depth. Executives see portfolio health. Managers see allocation grids. Individuals see their schedules. No role gets overwhelmed by irrelevant detail.
AI insights always show freshness timestamps, confidence signals, and data provenance. Users trust recommendations they can interrogate and verify.
Scores, summaries, and warnings live inside the views where decisions happen. Intelligence is never buried behind a separate analytics tab or chatbot sidebar.
Dense data requires calm design. Limited palette, generous cell padding, purposeful emphasis. Every pixel earns its place — no decoration for decoration’s sake.
Every allocation change shows the full impact chain — who’s affected, what’s overbooked, what shifts downstream. Managers commit with confidence, not hope.
Outcomes were measured across pilot teams during the initial deployment phase. Quantitative metrics were supplemented with qualitative feedback from stakeholder validation sessions across all three persona types.
Heat-map grid and inline editing reduced average allocation planning from days of email coordination to minutes of direct manipulation. Managers report recovering an entire day per week previously spent on logistics.
Real-time overallocation detection in the clone wizard and allocation grid caught conflicts before commitment. Shifted paradigm from reactive firefighting to proactive prevention.
Embedding AI summaries directly into existing views achieved high engagement without behavior change. Users don’t “use AI” — they just see smarter data. Validates the ambient intelligence approach over chatbot or separate-tab models.
Prototype-to-production workflow established 23 documented interaction patterns and 6 reusable component specs. New features leverage existing patterns, accelerating delivery by an estimated 40%.
Saveable filter states in the change log gave compliance teams reproducible audit trails. Monthly audit reports now run in seconds instead of hours of manual compilation.
All three persona types navigated the progressive disclosure IA successfully during validation. Executives stayed at L1, managers operated at L2, ICs used L3 — but cross-layer navigation was used naturally when needed.
Every project teaches as much about what to do differently as what worked well. This section is an honest accounting — the wins I’m proud of, the areas I’d approach differently next time, and the opportunities ahead.
Configuration interface for custom project metadata — Basics, Strategy & Alignment, People, Financials, and Delivery sections with field-type management.
AI-powered demand forecasting that predicts staffing needs from pipeline data before projects are formally sold — shifting from reactive to anticipatory allocation.
Gradually expanding AI automation from recommendations to semi-autonomous allocation with human approval gates — moving the automation spectrum marker rightward as trust is established.