liveBook · Manning

Self-service

Self-service is a mode in which users independently obtain resources or perform supported tasks without requiring an intermediary for each request.

How 6 Manning books explain it

Effective Platform Engineering

Self-service is a pattern in which users obtain resources or perform supported operations directly without depending on an intermediary for each request.

How it is used
Enables development teams to obtain platform capabilities and complete delivery tasks without waiting for another team to fulfill each request.
How deep it goes
Develops API-first interfaces, team-based access, tool integration, and adoption measures; defers a complete identity-implementation comparison.
Examples
Uses instant team onboarding, a portal-based microservice deployment, and replacement of a ticketed process with a measured interface.
What you can do after
Build it from scratch as an API-backed platform capability, then evaluate it through task time, onboarding, and adoption.

Read how Effective Platform Engineering explains self-service →

Effective Data Analysis

Self-service analytics is a practice in which stakeholders independently explore, query, and interpret data using prepared analytical resources.

How it is used
Enables stakeholders to answer routine data questions independently when analytics teams have limited capacity.
How deep it goes
Develops an iterative strategy of request review, stakeholder testing, guidance, and updates without prescribing one platform implementation.
Examples
Uses filtered product dashboards, pre-aggregated finance tables, and reports that replace repeated customer-subset requests.
What you can do after
Build it from scratch by identifying repeated questions, choosing suitable resources, testing them with stakeholders, and publishing guidance.

Read how Effective Data Analysis explains self-service →

Effective Conversational AI

A service interaction in which customers complete a task or obtain information without assistance from a human agent.

How it is used
Enables customers to complete tasks through a virtual assistant rather than receive instructions or immediately use a human agent.
How deep it goes
Develops flow-design choices, backend shortcuts, progress cues, and escalation paths; leaves integration implementation unspecified.
Examples
Contrasts a balance answer with FAQ guidance, reorders an insurance claim response, and simplifies spoken member-ID collection.
What you can do after
Evaluate/understand it by checking task completion and opt-outs, then reducing avoidable questions while retaining alternatives and agent routes.

Read how Effective Conversational AI explains self-service →

First-Party Data Activation

Self-service is a capability that allows users to perform tasks independently without ongoing assistance from specialized technical teams.

How it is used
Positions self-service as a way to remove data-team bottlenecks from first-party audience creation and campaign execution.
How deep it goes
Defines practical audience-design controls and compares adoption options, but defers technical how-to steps.
Examples
Uses audience dashboards, a marketing-technology comparison, vendor pilots, and GrowthLoop activation across email and paid media.
What you can do after
Evaluate/understand it by testing whether marketers can design and activate representative campaigns without ongoing technical support.

Read how First-Party Data Activation explains self-service →

Platform Engineering on Kubernetes

A self-service capability lets development teams provision, configure, or operate platform resources without direct intervention from platform engineers.

How it is used
Uses platform APIs to let development teams consume assembled cloud and operational capabilities independently.
How deep it goes
Defines self-service through platform APIs and team capabilities, but stops short of prescribing a single implementation.
Examples
Points to OpenShift and Tanzu as opinionated Kubernetes-based tools that can support out-of-the-box workflows.
What you can do after
Apply it via platform APIs to consume platform capabilities while reducing direct platform-engineer intervention.

Read how Platform Engineering on Kubernetes explains self-service →

Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

Self-service is an operational practice in which teams independently request, create, or modify resources without requiring another team to perform every change.

How it is used
Uses shared infrastructure modules to let application teams progress independently while preserving expert release review.
How deep it goes
Explains an approval workflow and a destructive-update failure, but stops short of specifying module standards or migration procedures.
Examples
Uses a Beans team PostgreSQL 12 upgrade that risks deleting an existing database.
What you can do after
Apply it via shared modules, staged approval, and specialist review for potentially disruptive infrastructure changes.

Read how Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform explains self-service →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.