Research

As explained in Effective Platform Engineering

User research is the systematic investigation of users’ needs, behaviors, experiences, and challenges to inform product decisions.

User research systematically investigates users’ needs, behaviors, experiences, and challenges so product decisions address real problems rather than assumptions. In platform engineering, it connects developer workflows and pain points to platform priorities, usability, and business outcomes. section 10.2.4 section 10.7.1

A practical research cycle combines:

• Interview developers, operations teams, and other stakeholders to discover workflow obstacles and unmet requirements. section 10.2.4 section 10.2.2
• Use surveys and observational studies to gather evidence about recurring behaviors, challenges, and expectations. section 10.2.4
• Analyze collected responses, summarize findings, and convert validated problems into roadmap priorities. section 10.2.5 section 10.2.2
• Revisit findings through feedback, stakeholder communication, and platform metrics to guide incremental improvements. section 10.2.4 section 10.2.2

From deployment pain to platform priority

A platform team discovers through research that developers spend significant time on manual deployments, causing delays and errors. It prioritizes automated deployment pipelines and self-service infrastructure provisioning, then uses feedback and metrics to assess whether workflows improve. section 10.2.2 section 10.7.1

Figure 10.4 Visual representation of the lifecycle of the platform-as-a-product approach, highlighting how to transition from vision and mission to a fully operational, developer-centric platform

Use the lifecycle visualization to connect research findings with platform vision, roadmap decisions, prototypes, feedback, and operational delivery. section 10.2.5

How Effective Platform Engineering covers it

How deep it goes

Details interviews, surveys, observation, response analysis, and feedback, but stops short of prescribing a single research method.

Examples

Uses interviews, surveys, observational studies, survey-analysis scripts, personas, prototypes, and deployment-workflow investigations.

What you can do after

Evaluate platform priorities through user evidence, summarize findings, and translate validated pain points into roadmap features.

How it connects

Connects user research with platform product management, developer experience, product roadmaps, stakeholder engagement, and KPIs.

liveBookmanning.com

Read Effective Platform Engineering on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Design for DevelopersUser research is the systematic study of users, their needs, behaviors, and responses to inform product decisions.
• 

  liveBookmanning.com
  Effective Data AnalysisResearch is the systematic investigation of a topic through study or experimentation to obtain new information.
• 

  liveBookmanning.com
  Architecture Modernization: Socio-technical alignment of software, strategy, and structureUser research is the systematic study of users' behaviors, needs, experiences, and feedback to inform product or service decisions.
• 

  liveBookmanning.com
  Everyday Data VisualizationThe systematic study of users' needs, behaviors, expectations, and experiences to inform design decisions.

Compare how 5 books explain research →

Related concepts

• user testingincludes · User testing is an evaluation method that observes or measures representative users interacting with a product or system while performing relevant tasks.
• contextual inquiryincludes · Contextual inquiry is a qualitative research method that studies users' activities and interactions in their natural environment.
• interviewuses · An interview is a structured or semi-structured conversation in which questions elicit information about a participant’s experiences, views, needs, qualifications, or requirements.
• platform product managerused by · A platform product manager is a product-management role responsible for understanding platform consumers, prioritizing value, and guiding platform strategy and evolution.
• assumptioncontrasts with · An assumption is a proposition or condition provisionally accepted as true or applicable as a basis for reasoning, planning, modeling, or action.
• continuous discoveryused by · Continuous discovery is the ongoing practice of researching users, needs, and opportunities throughout a product's design and development cycle.

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.