Whatagraph

What Stevin gets out of Whatagraph

Whatagraph is made to impress the recipient: data from multiple sources in a report that looks sharp, so a stakeholder gets it at a glance. We use it where the presentation counts and a raw export just does not convince. Where it pinches is that the emphasis sits on the form. A visually strong report shows neatly that something went wrong, but the report itself does nothing about it and it arrives at fixed moments, not when it matters. Whatagraph brings the data together nicely, but it does not flag and it does not follow up. That is the layer Stevin adds on top. Through the same channel data, Stevin reads along and gives a heads-up the moment something turns, with concrete follow-up underneath and a person reviewing every action that carries weight first. Whatagraph shows, Stevin watches.

What you pair it with

Whatagraph sits on the presentation side of your stack: it pulls data from your channels and makes a polished report of it, but it is not a workspace and not an early warning. Count on it living alongside your sources and bringing them together at fixed moments. In practice: use it to take stakeholders through what happened, and put something next to it that notices what is going on now. A nice report convinces, but it tells you too late that you should have intervened.

Common mistakes

• →Confusing a handsome report with intervening in time.
• →Letting the form win over the question of who reacts to the numbers.
• →Assuming combined data equals follow-up.
• →Only looking at fixed moments and missing ongoing deviations.