Services

Understand the work before you choose it.

A service defines a specific unit of work or ongoing support: its purpose, scope, responsibilities, method, outputs, dependencies, and conditions.

SkillBrix publishes an individual service only when its ownership, delivery readiness, and availability have been approved. This page explains how to evaluate that information and where to go when you are still defining the need.

See what a service definition covers
Business colleagues reviewing performance information together.
Clear scope, ownership, and delivery readiness

Catalog status

The catalog defines a standard, not a list of available services.

The current Service Catalog contains a provisional taxonomy of business areas. It does not approve individual services, delivery experience, or availability. For that reason, this page does not present taxonomy entries as service offers.

When a service completes the required readiness and approval process, its public description can explain what is included, who it is for, what participation requires, and how delivery is governed. Scope and status must remain current wherever that service is described.

How to evaluate a service

A useful service description makes the boundaries visible.

A service is not a broad area of expertise or a tailored response by itself. It is work with an accountable owner, defined scope, and clear conditions.

Overview and fit

The need addressed, relevant business situations, intended audience, suitability criteria, and known exclusions.

Scope and dependencies

Included work, boundaries, assumptions, prerequisites, customer responsibilities, dependencies, and decisions required.

Engagement approach

The approved method, phases, customer participation, review points, and responsibilities for the agreed work.

Deliverables and outputs

Defined work products, ongoing outputs where relevant, review points, formats, and acceptance conditions.

Outcomes and evidence

Intended changes and possible measures, distinguished from verified results, with sources, attribution, and limitations stated.

Related work and next steps

Relevant solutions, industries, approved methodologies, and a next service only when the catalog confirms it is appropriate and available.

Ownership and service conditions

Accountability, governance, availability, support or transition conditions, and the current approval status.

Choosing the right form of work

The business question should shape the engagement.

A service may be relevant only after the situation, decision, and responsibilities are understood. The engagement model describes how the parties organize the work; it does not establish that a service is available.

Depending on the approved scope, the work may be structured as consulting, advisory, implementation, capability building, training, a project, or a managed service. These terms describe different responsibilities and conditions, not interchangeable packages.

For example, consulting may suit a decision that needs structured analysis. Implementation requires an agreed target and acceptance conditions. A managed service requires explicit ongoing responsibilities, operating boundaries, and terms.

Fit is considered against the business need, customer readiness, dependencies, risks, decision rights, and the work that can be responsibly scoped.

Explore business solutions

Delivery and governance

Clear decisions carry through from discovery to handover.

An approved engagement defines which stages apply, who is responsible, and what evidence is needed to proceed. The sequence is tailored to scope and risk.

  1. Understand

    Establish the context, need, stakeholders, constraints, and decision requirements.

  2. Assess and plan

    Review relevant evidence, dependencies, options, scope, responsibilities, and acceptance measures.

  3. Deliver and govern

    Carry out the agreed work with proportionate quality reviews, decisions, risk controls, and change handling.

  4. Transition and review

    Confirm acceptance, transfer agreed knowledge or ownership, and review outcomes where measures are defined.

These stages describe the documented delivery model. They are not a commitment that every stage, method, or service is currently available.

After the agreed work

Completion should leave ownership clear.

A service may produce deliverables, operational outputs, and intended business outcomes. These are different things, and each needs an owner and appropriate review.

Accept and hand over

Review work against agreed acceptance conditions and transfer documentation, knowledge, access, or operational responsibility only as scoped.

Review what changed

Compare defined measures with their baseline when evidence and attribution permit. Treat intended outcomes as aims until supported by results.

Decide what follows

Close the work, continue with a separately approved scope, or identify another route. Ongoing support is never implied unless it is explicitly agreed.

Start with the work to be done

Discuss the scope behind your need.

Share the situation, decision, or work you are considering. A useful first conversation can clarify what is known, what needs validation, and whether an approved route may fit.

Discuss a service need