If you think about what I work on, what I actually produce at the end, it’s a document. Architecturally, it’s a diagram, an explanation of how things work, how they fit together, even down to questions like “what do we define a product as? When you say price, do you mean cost price or selling price?”, and things like that. It’s a document that defines all of that, as well as processes – this is how data comes in, this is who works on it, these are the systems involved… So on any given day, I’ll often have a document open on my screen and I’ll literally be going through it, identifying gaps in needs, checking dependencies and, if necessary, speaking to stakeholders to clarify, correct or add information. So I’m constantly planning ahead – I need to find such-and-such stakeholder to speak to, or I need to plan a workshop on this particular element, and so on.