HubScope
Home
Services
Product
How to start
Contact
Today that takes three days of forwarded email, and the room still cannot stand behind the number. HubScope is a living map of your systems, kept true by the people who run them, so the answer comes off the map instead. You ask in the language model you already use, and it ends on the person who confirmed it.
So it lives in heads, in a diagram from 2022, in a spreadsheet one person keeps, and it leaves when they do. The alternative is not a better diagram. It is giving that knowledge an address: the people who know record it against the system itself, signed and dated, and anyone reaches it by looking at where that system sits.
Rates Billing cannot move before the rating year closes, and when GIS goes down its nightly load fails without saying so. Neither fact is written anywhere.
Recorded against Rates Billing itself, in Hemi Petera’s own words, with his name and 14 July beside each one.
Nobody needs to know he knew them, or where he would have filed them. And it is not one system: every box on this map holds a record like it, which is why an answer about this estate comes back with a name and a date on it.
Pick a seat. On the left, how the question gets answered today; on the right, the same question put to the map, ending on a person.
For Thursday's ELT paper I need Option 0 on one page: what we actually run, and what carries forward if we stand still. Who can pull that together by Wednesday?
Will do. The last full picture is the 2022 landscape review; enterprise architecture hold it and will refresh what they can. Priya to confirm rates, Jo to cost standing still.
On leave until Thursday. For rates queries, please contact the rates systems analyst.
Marcus, forwarding it on: that role has been vacant since March.
About a hundred and twenty boxes, half with owners, three marked TBC. The analyst who kept it left last year; her v8 draft never reached the shared drive. 'Treat as indicative.'
Our 2024 roadmap deck (attached) counted eighty-four applications with your teams; happy to come back on which are still live. We could scope a discovery phase.
One of the TBC boxes: a server nobody owns. Dave Lindqvist sees a job fire on it at two every morning, feeding something nobody can name. Nobody has dared switch it off.
Your chaser to Marcus meets an out of office: vendor workshop until Wednesday lunchtime. Enterprise architecture are chasing owners through each GM; two replies, both from memory.
Carry-forward from the ledger: last year's licences plus CPI, forty-odd vendors. Which vendor is which system, and what breaks if we stop paying, is not something finance holds.
Two counts on the table, the Visio and the vendor deck, neither with owners. Marcus, packing up: not where I want it, but it is what we can stand behind tonight.
First question in the room: which of these do we still run? Nobody can say. Option 0 minuted as indicative; paper deferred pending a baseline the room believes.
Decision slips a month.
Three counts, as the map has them:
The two carrying the most dependency are rates billing and the legacy CRM, which 22 systems still read from. Do nothing, and every one of those carries forward another year.
Read from the Northwind council living map. Owners confirmed 14 July.
Put it under Marcus Reid's name: he confirmed the counts on 14 July, and every system on the page carries the person who signed it off. You never opened the map. You did not need to.
Tell us where you sit and the kind of place you sit in, and we will build the map for it: the systems, the owners, and the questions someone in your seat actually ends up asking. We make each one to order rather than keeping a library to click through.
Want to see it on your own estate? Book a session.
