Gfacility

Refine & scale

Roadmap evolution

A living roadmap fed by KPI signals, business questions and maturity scores. Not a chart on paper — a list with direction, weight and cadence.

Updated May 18, 2026

Refine · 6.5

Why this matters now

Most implementations have a nice roadmap at the end of phase 1 — and then it stops. Three months later no one remembers the priorities, and not until contract renewal does something surface again. A living roadmap with clear inputs prevents that. It’s not a Gantt chart; it’s a working document.

What do you deliver?

Roadmap format

Three horizons: Now (0-3m), Next (3-9m), Later (9-24m). Items elaborated, not endless.

Input sources

KPI signals, maturity gaps, AI promotions, user requests, product updates.

Prioritization model

E.g. WSJF, MoSCoW or your own ICE score. Unambiguous, not "we'll see".

Cadence

Weekly triage of new work, quarterly grooming, yearly recalibration with the steering committee.

Key questions

  1. 1Who is product owner of the roadmap? One person, with an explicit mandate — not a committee.
  2. 2Which sources feed the roadmap — dashboards, maturity model, AI status report, helpdesk business requests, Gfacility product updates?
  3. 3Prioritization model — WSJF (value / effort), MoSCoW, ICE (Impact × Confidence × Ease)? Pick one and stick with it.
  4. 4How big is an item — everything on one layer, or categories (quick fix / change / project)? Three scales gives clarity.
  5. 5Link to budget — do you have a fixed budget allocation (e.g. 0.5 FTE config + €X consultancy per quarter), or request-by-request?
  6. 6Communication — how do you make the roadmap visible to stakeholders without it becoming "a promise"?
  7. 7Saying no — how do you turn down a wish? With arguments and alternatives, not "no capacity".
  8. 8Effect measurement — once an item is delivered, how do you measure that it actually improved the target KPI? Link to continuous-improvement log.
  9. 9Strategic items — when do you tackle big steps (new module, integration, phase 2)? How do you link to the business cycle?
  10. 10Yearly recalibration — once a year, radically revisit the roadmap with the sponsor and steering committee based on data and business direction.

Template — Living roadmap

Now — 0-3 months

  • • Extend KB for IT (top-10 questions)
  • • Promote no-show detection to level 3 (excl. boardroom)
  • • Automate ERP export script
  • • Lift sales-team adoption (targeted 1-on-1s)

Next — 3-9 months

  • • HR questions via Gfacility (new module)
  • • Wider mobile-app rollout
  • • Re-evaluate auto-routing P3 after workgroup-skill update
  • • Finalize Sodexo catering integration

Later — 9-24 months

  • • Roll out full asset management
  • • IoT sensors in 3 largest buildings
  • • AI auto-resolve for password resets
  • • International rollout (France, Germany)

Template — Item fact sheet

Field Value
TitleNo-show detection to level 3
Source signalAI status report Q3: accuracy 91%, trust 88%
Target KPINo-show rate from 12% → 8%
ICE scoreImpact 8, Confidence 7, Ease 6 → 336
HorizonNow
ScaleChange (no project)
PrerequisitesBoardroom exception, communication template
OwnerFM lead + configurator
Effect measurementCompare no-show rate after 4 and 8 weeks