A candidate value stream may look coherent as a domain, yet still leave its team unable to work effectively. Independent service heuristics (ISH) help test whether a proposed domain boundary also makes sense as a team and software boundary, and whether the value stream has the conditions it needs to succeed. The technique can also assess an existing value stream. section 11.3 section 11.6
ISH is a checklist of ten heuristics covering value, product decisions, dependencies, and other concerns. Each provides questions and guidance. Its purpose is to structure conversation before investing in changes—not to give one architect a tick-box approval process. Bring together people with different perspectives, including business leadership, product, and engineering. section 11.3.1 section 11.6
For a candidate value stream:
- Work through all ten heuristics, agreeing on satisfaction criteria for each. A simple record is thumbs-up, thumbs-down, or more investigation needed. section 11.3.1
- Use disagreements or uncertain answers to identify concerns for follow-up sessions. Complement a heuristic with other techniques where useful. section 11.3.1
Testing impact and value
Ask whether the scope offers engaging domain or product challenges and creates recognizable value for customers and the organization. Is it large enough to have impact? Would people be motivated to work on it? A “no” is not automatically a rejection: a supporting or generic subdomain may be less engaging but still make a viable value stream if that constraint is understood. The discussion may instead point toward refining its boundary. section 11.3.1
A favorable assessment raises confidence; an uncertain one gives stakeholders specific issues to investigate. Independence is not a permanent certification. Team arrangements evolve, so continue to notice awkward interactions, excessive collaboration, or a falling delivery cadence. section 11.3.1 section 11.6
