A year ago I shared a simple one‑page canvas called the Evidence Box.
The OG article on the Evidence Box
It came from a very specific kind of moment: You are under pressure to decide. Everyone has a strong opinion. You have scattered notes, a few metrics, and no time. The easiest path is a neat slide and a fast “yes.”
The Evidence Box was my way of forcing myself to pause long enough to answer three questions:
What do we actually know about this problem?
How are people really behaving around it?
What have we already tried and learned, even if we have forgotten?
That little canvas did better than anything else I had ( and have) put into the world. It also made something very clear to me:
There is a lot of demand for tiny, practical tools that help you think better when stakes and noise are high.
Since then, I have been quietly building around that idea.
Distilling 15 years of BA work into patterns that fit on one page.
Turning “I keep seeing this mistake” into something you can put on a desk in front of a team.
Focusing on the boring but high‑leverage moments: scoping, alignment, deciding what not to do.
Two things came out of that work in the last few weeks that I am finally ready to share with you today.
This is the course I wish I’d had when I fell into business analysis. It is not “BA theory.” It is 90 days of doing the actual work:
Mapping real processes with real complexities.
Framing problems in language stakeholders recognize.
Writing just‑enough requirements, not 80‑page specs.
Running conversations that reduce noise instead of amplifying it.
The Evidence Box is woven into it as a backbone: you keep coming back to “what do we know, how do people really work, what did we learn from the last attempt?”
If you have been doing BA work without a playbook, this is my attempt at giving you one.
Notion Hub - Your First 90 Days as a Business Analyst
While teaching and consulting, another pattern would not leave me alone:
On paper, a change looks fine.
In practice, a few people quietly absorb all the extra work it creates.
No one planned for the monitoring, the exception handling, the explaining, the stitching into old systems. That “invisible work” is usually where good ideas go to die.
The Invisible Work Canvas is my answer to that. It sits next to the Evidence Box and asks a different question:
“If we say yes to this change, who will actually be doing what, and is that load even possible?”
It came directly out of watching AI pilots and process changes that were smart in theory but brutal in practice.
Notion Tool - The Invisible Work Canvas
These three pieces now form a small, coherent spine:
Evidence Box – base decisions on something better than enthusiasm.
Invisible Work Canvas – see the real cost of a “yes” before you commit.
90‑Day BA – build the skills to do this kind of thinking as your default.
If you have been following along for a while, thank you. The fact that the Evidence Box landed the way it did is what made me take this work seriously enough to keep going.
I’ve added links and screenshots above if you want to explore any of them.
As always, if you use these tools and they change how a conversation goes in your world, I would love to hear that story.
Until next time,
Pragati
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.