When describing a system, begin with the parts that carry the request. Name the client, the service it calls, and the place data is stored. Then add the connections that explain the path.
Add one decision at a time
Ask what each part is responsible for. If a service handles two unrelated jobs, splitting it may make the design easier to reason about. If two boxes always move together, ask whether the distinction matters yet.
Review the path
Follow a request from its starting point to its result. Where could it wait? What happens when a component fails? Who owns the data at each step? Those questions often reveal a missing connection or an assumption hidden behind an arrow.
In Lycana, start by describing the client, service, and data store. Add the request path, then revise one connection when the review reveals a missing wait or failure. You can use spoken or typed instructions and edit the diagram directly on the canvas.
