Rebuild plans fail quietly when boundaries exist only in a consultant’s head. A delivery vendor then invents their own map, and six months later nobody can say which team owns partner callbacks.
Boundaries that travel
Write boundaries as obligations, not only as boxes on a diagram:
- Which system is the source of truth for member identity
- Which team may change partner callback contracts
- Which content types migrate with the portal versus stay in a document store
- Which monitoring alerts page the portal team versus an integration team
If a boundary cannot be stated as an obligation, it will not survive handover.
Avoiding the “platform” fog
Teams sometimes label every shared service a “platform” and stop thinking. Prefer concrete names: session service, document store, partner gateway. Portal Riverpoint’s rebuild planning documents use those names so Thai and regional contractors can price work without decoding metaphors.
Test with a stranger
Give the boundary list to someone who did not attend discovery. Ask them to assign an incident. If they cannot, rewrite until they can. That test has saved more programmes than any ornamental architecture poster.