Skip to content
LUWEE

Plan

Demand and prioritization: Choose better before you start executing.

The problem
Requests arrive by email, in meetings and in spreadsheets. Without shared criteria, whoever pushes hardest gets priority, and the budget runs out before the demands that matter most.
With LUWEE
Every demand goes through a cycle with evaluation, prioritization and decisions on record. Selected demands become projects with the project charter already filled in.
Representation of the Prioritization Workbench with fictitious data. Swipe to see the full screen

How it works

The flow, step by step.

  1. 01

    Guided intake

    A three-step wizard (information, context and benefits, review and submit) records the demand and its technical owner.

  2. 02

    Business and technical evaluation

    Evaluation models split into sections, each with its own owner, resolved by organizational unit. Pending items receive reminders.

  3. 03

    Prioritization framework

    Scales, criteria and dimensions from your environment, organized into versioned models, so demands are compared on equal terms.

  4. 04

    Cycle, scenarios and decision

    Cycles scoped by unit, budget and capacity. In the Workbench, the matrix, the ranking with cut line and scenarios support the decision.

  5. 05

    Conversion into projects

    Selected demands are converted in bulk, and the project charter starts pre-filled with what the demand brought in.

Key features

What makes the difference day to day.

Demand pipeline

List and Kanban by lifecycle stage, with configurable columns and filters that answer everyday questions.

  • “Who has it”, “Idle for” and “I need to act” filters
  • Demand status kept separate from the latest cycle decision
  • Requests for additional information recorded in a structured way

Cycles with Control Tower

Each prioritization cycle has a pending-items dashboard for whoever runs the process.

  • View by owner and KPIs that filter the list
  • Bulk demand selection
  • Canceling the cycle cancels the evaluations it triggered

Prioritization Workbench

Configurable matrix, ranking with the reason behind each position, scenarios and list, with constraints calculated on the server.

  • Budget and hours constraints applied to the ranking
  • If someone else changed the decision, the system tells you who
  • Audit trail with before, after, reason and source

Who it’s relevant for

  • Executives and committees

    Decide with the ranking, scenarios and constraints in view.

  • PMO

    Runs cycles and tracks pending items without chasing people by email.

  • Requesting areas

    Know what stage the request is in and who has it.

  • Evaluators

    Receive only the sections assigned to them, with reminders.

FAQ

Before the demo.

Can I use my organization’s prioritization criteria?

Yes. Scales, criteria and dimensions are part of your environment’s catalog and are organized into versioned models, which can be duplicated to create variations.

Who evaluates each demand?

The evaluation model is split into sections, each with an owner. When the cycle is triggered, LUWEE resolves the owners by organizational unit and sends a consolidated notification.

What happens after a demand is selected?

It can be converted into a project, including in bulk. The project charter starts pre-filled with the demand’s information.

How are decisions recorded?

Every decision in the Workbench creates an audit record with the previous state, the new state, the reason and the source. The demand also keeps a history of evaluation and decision events.

Demo

See LUWEE applied to your challenge.

Tell us how your organization works today. We’ll show you Demand and prioritization with the platform’s real screens and how the module connects to the rest.

  • Led by the challenge you point out
  • With people who know the product inside out
  • No purchase commitment

Fields marked with * are required.

Optional, with area code.

Consent