Lakshmanan I
Enterprise Research Platform · Web

Consumer Research Platform
Seven tools. One front door.

ICLS unified a fragmented consumer-research estate behind a single entry point — an answer engine over historical studies, five capability groups organised by intent, and a governed request-to-approval workflow with spend visible in one view.

Role
Lead UX/UI Designer
Client
Fortune 500 CPG
Platform
Enterprise Web
Team
BA · Dev · Data · Governance
ICLS · Discovery home
ICLS discovery home with the answer engine above the fold and five capability cards below

The answer engine sits above the fold, framed as a question rather than a search box. Below it, five capability cards route to every tool in the estate.

Tools used
    01 — Problem

    Seven specialist tools, and no front door

    Consumer research ran across seven disconnected specialist tools. Researchers memorised where each one lived, approvals were tracked in email threads, and completed studies were archived somewhere unsearchable — so the same research was commissioned twice.

    • 01Fragmented estate

      Seven tools with separate entry points, separate logins and no shared vocabulary between them.

    • 02Approvals lived in email

      Status existed only in someone's inbox. "Where is my study?" had no authoritative answer.

    • 03Past research was invisible

      Completed studies were archived but not searchable, so prior work was rarely reused.

    This looked like a UI brief and was really an information architecture and governance brief. The decisions that mattered were structural, not visual.

    02 — Research

    Five roles, one contested workflow

    UserPrimary goal
    Study Owner / ResearcherDesign and execute a study without relearning the tool estate
    Approving ManagerReview and sign off study design on a defensible basis
    Finance ApproverValidate budget before commitment
    Portfolio AdminOversee the portfolio and report fiscal-year spend
    Lead SupplierReceive scope and deliver against agreed terms
    Key findings
    • 01Onboarding took weeks

      New researchers learned tool locations by asking colleagues, not by using the product.

    • 02"Where is my study?"

      The single most-asked question in the estate — and the one nothing could answer.

    • 0320+ governed fields

      The PO request carried more than twenty fields, each with its own compliance rule.

    • 04Search intent was conversational

      People asked questions in sentences, not keywords, and expected an answer.

    • 05Compliance arrived too late

      AI, IT and legal declarations surfaced after commitment, forcing rework.

    • 06Finance needed one number

      Portfolio owners wanted a single fiscal-year spend figure, self-serve.

    03 — Insight

    Organise by intent, not by inventory

    • Intent beats inventory

      Users do not think "which tool" — they think "I need to learn something". Grouping by intent made seven tools legible as five capabilities.

    • Search is the homepage

      If the top question is conversational, the answer engine belongs above the fold, framed as a question rather than a search box.

    • Status is an object

      Approval stage deserved to be a first-class entity with a named owner and a timestamp — not a line in an email.

    • Governance belongs in flow

      Compliance declarations captured inside the request, with inline guidance, prevent rework after commitment.

    04 — Constraints

    Enterprise realities that shaped the design

    ConstraintDesign response
    Seven tools could not be rebuiltA federated portal that routes to existing tools rather than replacing them
    Governed multi-party approvalsA five-stage stepper with named owners at every transition
    Global participating marketsAmounts carried in both local currency and USD
    AI, IT and legal complianceDeclarations captured upfront inside the request flow
    Very long request formsSectioned into General and Key Information, with save-as-draft
    Fiscal-year finance reportingPortfolio view with fiscal-year switch and Excel export
    05 — Information Architecture

    Architecture was the design

    The portal federates an existing estate. Three core objects carry the model, and every module in the portal resolves back to one of them.

    StudyWhat is being learned
    ApprovalWho signed off, when
    KnowledgeWhat already exists
    Portal modules
    ICLS Portal · Corporate SSO

    Home

    Answer engineCapability hubFirst-login tour

    Consumer Governance

    Generate a PO (CRP)MMP purchaseMy StudiesApprovals

    Consumer Insights

    Global historical studiesStudy records

    Consumer Concept

    Concept generationConcept testing

    Consumer Analytics

    Analysis toolsAssessment

    Resources

    GuidanceSpend reportingDIY concierge
    The home hub — five intents
    IntentWhat sits beneath it
    DesignGenerate a PO (CRP), MMP purchase, My Studies, Global Historical Studies
    LearnHistorical research retrieval and guided study selection
    GenerateConcept generation and creative development tools
    AnalyzeAnalytics and data interpretation capabilities
    AssessValidation, testing and assessment tooling

    The IA tree was the artefact that got seven tool owners to agree. It unblocked the build more than any screen did.

    06 — Core Flows

    Discover, request, approve

    Three flows carry the platform. The first prevents duplicate research, the second governs commissioning, the third makes status self-evident.

    Discovery flow
    1. 01Ask

      Natural-language question, not keywords.

    2. 02Retrieve

      Matching historical studies surface.

    3. 03Evaluate

      Scope, method, markets, deliverables.

    4. 04Decide

      Reuse existing or commission new.

    5. 05Route

      Hand off to the right capability.

    Study request flow
    1. 01Define

      Title, owner, organisation, function.

    2. 02Scope

      Category, technique, methodology, markets.

    3. 03Declare

      Supplier, IT, AI and legal compliance.

    4. 04Justify

      Purpose, success criteria, background.

    5. 05Submit

      Save as draft or commit the study.

    Approval & execution flow
    1. 01Planned

      Study created and scoped.

    2. 02Design Approval

      Manager signs off on method.

    3. 03Financial Approval

      Finance validates the budget.

    4. 04Execution

      Supplier delivers against scope.

    5. 05Completed

      Deliverables filed and searchable.

    Every transition records step, date, status and owner — so the audit trail builds itself rather than being reconstructed later.

    07 — Journey Maps

    Three roles, three definitions of done

    Each map compares actions, needs and the corresponding design response across one commissioning cycle.

    Stage
    Arrive
    Discover
    Request
    Declare
    Track
    Close
    Action
    Sign in via corporate SSO.
    Ask a question about prior research.
    Complete the governed CRP form.
    Confirm supplier, IT, AI and legal.
    Follow the approval stepper.
    Collect deliverables and proof of performance.
    Need
    Know where to start.
    Avoid duplicating existing work.
    Not lose progress on a long form.
    Understand what each rule means.
    Know the current owner.
    One authoritative record.
    Response
    Answer engine plus first-login tour.
    Natural-language retrieval over the archive.
    Sectioned form with save-as-draft.
    Inline guidance beside each declaration.
    Five-stage stepper with named owners.
    Study record with files and CRP document.
    Stage
    Receive
    Assess
    Verify
    Decide
    Hand on
    Audit
    Action
    Pick up a study awaiting design approval.
    Review scope, method and markets.
    Check compliance declarations.
    Approve or return with comment.
    Pass to financial approval.
    Revisit history when questioned.
    Need
    A queue, not an inbox.
    Enough context to judge.
    Confidence nothing is missing.
    A defensible basis.
    Clear transfer of ownership.
    Durable evidence.
    Response
    Approval queue with visible stage.
    Study details panel with sub-records one tab away.
    Declarations captured in the request.
    Stage actions with mandatory remarks.
    Named owner on the next stage.
    Approval history: step, date, status, assignee.
    Stage
    Oversee
    Filter
    Reconcile
    Report
    Govern
    Improve
    Action
    Open the fiscal-year portfolio view.
    Filter by owner, type, status and spend.
    Check PO upload progress against studies.
    Export the portfolio to Excel.
    Maintain governed pickers and taxonomy.
    Tune guidance from recurring errors.
    Need
    One committed-spend number.
    Find exceptions fast.
    Know what is outstanding.
    Self-serve finance reporting.
    Consistency across the estate.
    Fewer returned requests.
    Response
    Fiscal-year total above the table.
    Column filters and nine colour-coded statuses.
    PO upload shown as a progress fraction.
    Refresh plus Excel export.
    Centrally governed field lists.
    Inline guidance authored per field.
    08 — Design Principles

    Four rules that settled every argument

    • 01Intent before inventory

      Group by what a person is trying to do, never by which team owns the tool.

    • 02Status is always visible

      Every study shows its stage and its current owner without anyone having to ask.

    • 03Governance in the flow

      Compliance is captured where the work happens, not bolted on after commitment.

    • 04Reuse before commission

      Show what already exists before offering to spend money on something new.

    09 — Approach

    A process made visible at every gate

    1. 01Research
    2. 02IA Tree
    3. 03User Flows
    4. 04Wireframes
    5. 05Visual Design
    6. 06Prototype
    7. 07Testing
    8. 08Handoff
    How insight became decision
    InsightDesign decisionWhere it landed
    People think in intentFive capability groups above the tool estateCapability hub
    Search intent is conversationalAnswer engine with popular-search promptsDiscovery home
    "Where is my study?" dominatesFive-stage stepper as a first-class objectStudy record
    Compliance arrives too lateAI, IT and legal declarations inside the requestGenerate a PO (CRP)
    Long forms get abandonedSectioned layout with save-as-draftCRP form
    Finance needs one numberFiscal-year total with filters and exportMy Studies
    10 — Readability

    A 20-field form that people finish

    The governed request was the densest surface in the product. Legibility was solved at three levels.

    • FORMSectioned disclosure

      General Study Information and Key Information split a 20-field request into two readable passes.

    • PORTFOLIOStatus as colour

      Nine colour-coded work statuses make the exceptions in a long table visible before it is read.

    • PROGRESSFractions, not flags

      PO upload renders as a progress fraction, so partial completion is legible at a glance.

    Supporting patterns
    PatternWhy it exists
    Governed pickersCategory, technique, methodology and markets come from centrally maintained lists, so data stays comparable across the portfolio
    Inline guidanceEach declaration carries its rule beside the field, removing the need to consult a separate policy document
    Dual currencyAmounts render in local currency and USD together, so global markets and finance read the same record
    11 — Testing & Iteration

    What changed once researchers used it

    Problem

    The long request form was abandoned midway when a researcher had to go and find a supplier detail.

    Solution

    Save as Draft, with drafts surfaced in My Studies so an unfinished request is never lost.

    Problem

    A keyword search box returned nothing useful, because people typed whole questions.

    Solution

    An answer engine framed as a question, with popular-search prompts to teach the interaction.

    Problem

    Compliance declarations were misread, causing requests to be returned after financial commitment.

    Solution

    Guidance authored inline beside every AI, IT and legal declaration at the point of answering.

    Problem

    Approvers could not tell whether a delay was theirs or somebody else's.

    Solution

    Approval history recording step, date, status and assignee for every transition.

    12 — Design System

    Built on the client design system

    ICLS was composed from the client's existing enterprise component library, extended only where the governance workflow demanded new patterns.

    Components extended
    • Approval stepper

      A five-stage horizontal stepper carrying stage name, owner and timestamp — reused on every study record.

    • Governed field group

      A picker paired with inline guidance, used for every centrally maintained taxonomy field.

    • Portfolio table

      Column filters, nine status colours, progress fractions, refresh and Excel export in one dense surface.

    The value was consistency of meaning — a status colour means the same thing on the home hub, the portfolio table and the study record.

    13 — Final Design

    The platform in use

    Discovery Home

    The answer engine sits above the fold, framed as a question rather than a search box. Below it, five capability cards route to every tool in the estate.

    • Natural-language retrieval over historical studies
    • Popular-search prompts that teach the interaction
    • Five intent groups: Design, Learn, Generate, Analyze, Assess
    • Corporate SSO with a first-login tour
    Discovery home
    ICLS discovery home with answer engine and five capability cards
    My Studies — the portfolio view
    • One number, one year

      Fiscal-year total planned amount sits above the table, with a year switch beside it.

    • Every study, one row

      Owner, type, spend and work status across nine colour-coded states.

    • Progress, not flags

      PO upload renders as a fraction, so partial completion is readable at a glance.

    • Self-serve reporting

      Column filters, refresh and Excel export remove finance's dependency on a request.

    Study Record & Approval
    • Five-stage stepper

      Planned → Design → Financial → Execution → Completed, answering "where is my study?" on sight.

    • Details panel

      Owner, dates and amounts in both local currency and USD, with sub-records one tab away.

    • Supplier and history

      Lead supplier name and contact, plus approval history by step, date, status and assignee.

    • Documents

      The latest CRP document with copy-link and download.

    Modules delivered
    ModuleCapability
    Answer EngineNatural-language retrieval across historical studies with popular-search prompts
    Capability HubFive intent groups routing to every tool, with inline guidance
    Generate a PO (CRP)Governed study request: scope, method, markets, supplier and compliance declarations
    MMPAdhoc data purchase path without raising a full study
    My StudiesPortfolio and drafts, fiscal-year spend, filters and Excel export
    Study RecordApproval stepper, budget, proof of performance, proposal, markets and files
    Global Historical StudiesSearchable cross-market archive of completed research
    ResourcesGuidance, spend reporting and the DIY research concierge
    14 — Impact

    What it added up to

    Platform outcomes
    • 7 → 1

      Fragmented tools unified behind a single front door

    • $800MM

      Fiscal-year research spend visible in one view

    • 5

      Approval stages, transparent with named owners

    The spend figure is the fiscal-year total planned amount surfaced by the portfolio view.

    Business outcomes
    • Closed the discovery gap

      Historical research became searchable in natural language, so prior work is reused rather than re-commissioned.

    • Made the approval chain visible

      Sign-off moved from email threads to a visible queue with named owners and timestamps.

    • Embedded compliance

      AI, IT and legal declarations are captured upfront, removing rework after financial commitment.

    • Gave finance self-serve reporting

      Fiscal-year committed spend is available on demand, without raising a reporting request.

    15 — Reflection

    Architecture was the design

    This project looked like a UI brief and was really an information architecture and governance brief. The decisions that mattered most were structural: naming groups by intent, treating status as an object, and putting compliance inside the flow. None of them are visible as a component, and all of them are why the platform works.

    • What I learned

      Unifying an estate is a diplomacy problem before it is a design problem. The IA tree was the artefact that got seven tool owners to agree, and it unblocked the build more than any screen did.

    • What I would improve today

      A personalised home based on role and study history, predictive approval-time estimates, AI-assisted form completion from prior studies, and a dedicated WCAG 2.1 AA pass on the dense portfolio table.