Back to Insights

Designing Maximo Start Centers That Drive Daily Adoption

Maximo Start Centers work when they match real roles and tasks. Patterns for landing pages that speed work, not clutter dashboards.

Maximo Best PracticesStart CentersUser AdoptionMaximo ManageApplication Designer

A Maximo Start Center is often the first screen a user sees after sign-in. When it is well designed, it shortens the path from login to productive work. When it is poorly designed, it becomes wallpaper: colorful, occasionally updated, and ignored. The gap between those outcomes is rarely technical capability. It is requirements discipline and role clarity.

This article sets out practical patterns for Start Centers in Maximo Manage (whether users work in the Graphite-based interface or the Classic UI) so landing pages reinforce process, not vanity metrics.

Why Start Centers Underperform

Three failure modes recur across implementations.

One template for every role

A single Maximo Start Center lists every portlet the project team thought might be useful. Planners, technicians, and buyers see the same charts. No one sees their next actions clearly, so they navigate away immediately.

Metrics without owners

Portlets display corporate KPIs that no individual can influence from Maximo. Utilization curves and backlog totals look impressive in steering meetings but do not tell a technician what to do before the end of shift.

Stale content

Portlets point to saved queries that nobody maintains. As data volumes grow, performance degrades or results become misleading. Users learn not to trust the landing page.

These are configuration and governance problems. They are fixable without custom code if you treat the Start Center as part of the operating model, not as a one-off build task during go-live.

Design Around Jobs, Not Org Charts

Start with concrete jobs: approve purchase requisitions, release work for a crew, review overdue PMs for a route, confirm goods receipt. Each job implies a portlet type: result sets, KPI counters, quick inserts, links to favorite applications.

Map portlets to roles, not department labels

Map portlets to roles (security groups), not to department names on an organization chart. Departments are unstable; the work itself is more durable. A “maintenance supervisor” Maximo Start Center might combine:

  • A result set of work orders in WSCH (or your equivalent status) for their sites
  • A KPI for overdue inspections tied to regulatory assets
  • Quick launch links to the Work Order Tracking and Labor Reporting applications

Planners need different defaults: unapproved work, material shortages, and contract labor limits. If both groups share one template, you optimize for neither.

Use Application Designer and Start Center tools consistently

Application Designer and Start Center configuration are the standard tools for this work in Maximo Manage. The same configuration concepts apply regardless of whether users consume screens through the Graphite UI or the Classic UI; the landing experience should still be intentional and maintained.

Keep Portlets Actionable and Bounded

Every portlet should answer one of two questions: “What do I do next?” or “Is there a problem I must escalate?”

Result sets and query bounds

Result sets work best when they are narrow: filtered by site, crew, supervisor, or a controlled work type. Cap row counts or use status filters so the portlet stays fast. Heavy, unbounded queries are a common cause of poor perceived performance on sign-in.

KPIs with a drill path

KPI portlets should tie to thresholds that trigger behavior: for example, count of work orders past target start date for priority 1 assets. Pair the number with a drill path (link to the underlying query or application) so users can move from signal to record in one or two clicks.

Workflow and in-basket visibility

In-basket and workflow integration belongs on Start Centers for roles that approve or assign work. If your organization uses workflows and escalations, surfacing the in-basket on the landing page reduces email chasing and duplicate status checks.

If a portlet does not change what someone does this week, remove it or move it to a management dashboard outside the daily path.

Align With Broader Data and Integration Discipline

Start Centers display what the system holds. If asset hierarchies are messy or integrations feed duplicate work orders, the landing page amplifies the noise. Teams that invest in clean object structure and integration contracts get more reliable portlets and faster queries by default.

For programs moving toward IBM MAS, landing pages sit alongside a wider platform shift: suite applications such as Monitor or Predict consume their own data quality rules, while Maximo Manage remains the system of record for work and asset master data. Keep Maximo Start Center content inside what Manage actually controls (work, assets, inventory, procurement) so users are not asked to interpret data that is not yet trustworthy in the CMMS. Larger platform programs often sequence this work alongside EAM delivery and data readiness; the landing page should still reflect only what is operationally sound in Manage at each cutover stage.

Governance: Owners, Cadence, and UAT

Assign a named product owner for each role-based Start Center template. That owner approves portlet changes, reviews query performance quarterly, and retires portlets that no longer match process.

Include Start Center changes in user acceptance testing when you change workflows, statuses, or security groups. A portlet that still filters on a retired status code silently trains users to ignore the page.

Run a short annual survey or workshop with each major role: “Which portlet did you use last month?” Anything unused twice in a row should be a candidate for removal. Simplicity beats completeness on the first screen after login.

Takeaway

A Maximo Start Center is a small part of the product, but it sets the tone for adoption. Treat it as a living product: role-specific, query-bounded, and owned. That is how landing pages earn daily use instead of a single glance before users open the applications menu.

Sources