Skip to main content
Version: 0.7.0

Startup profile

Purpose​

The profile helps a small team see the whole product, assess technical dependencies quickly, and preserve knowledge during frequent change. Its main value is a shared delivery map, not classification precision.

Minimum scope​

  • an actor receiving an outcome;
  • a service or key use case;
  • a system as the product boundary;
  • a component when it is independently developed or deployed;
  • an integration or dependency;
  • a deployment or clear execution environment.

Information may be labeled on an integration. A compute resource may be abstract, such as “managed cloud.” Channel, process, capability, interface, and network are added only when actually needed.

Useful questions​

  • Which parts must change for a new user scenario?
  • Which external dependencies can stop the product?
  • What is deployed independently, and who owns it?
  • Where is the single point of failure?

Profile boundary​

Do not describe every library as a component, every API operation as an object, or an organizational process that does not exist. When discussions regularly involve different channels, business-outcome owners, and reused data, move to the stable-business profile.