13: Insight Inc.
In the last email (subject: Guidance Inc.), I shared how Notion had given us the ability to embed guidance and resources into pre-defined workflows, meaning people have exactly what they need at the moment it’s needed.
Mind. Blown.
From the perspective of performance improvement, this was huge - and something I had never seen implemented before at a system level. Regardless of whether or not organisations had access to Notion, this was the perfect example of how we should be improving performance.
In my mind, this had become the benchmark against which all other performance support solutions would be measured.
This was a performance guidance system.
But it turns out this was just the tip of the iceberg.
As I mentioned in previous emails, data in Notion is stored in user-created databases. And we can create as many of these as we like.
Not only that, but databases can be connected. This means you can be looking at one database, and it can pull in data from another. And vice versa (the proper term being relational databases).
But it wasn’t until I explored this functionality more deeply that I realised the implications. Because not only could we guide people on doing the right things and then show them how to do them, we could also surface insights from others.
So, in the example we’ve been discussing, workflows could draw upon other databases to surface:
Examples of previous good outputs
Common mistakes from past attempts
SME tips linked to this task type
Relevant policies or reference materials
Let’s imagine how this might work using my video workflow:
Brainstorm video ideas
Research high-ranking titles
Write script
Design storyboard
Set up camera and lighting
Record video
Edit video
Write description
Publish to YouTube
Share on socials
Now, let’s imagine a couple of my colleagues also make videos. And because they’re using the same workflow template, they also work through the same steps. After each step, the workflow might ask: “What did you learn that would help someone do this step better next time?”
So, after writing the script, my colleague might add: “The only requirement for the first ten seconds of the video is to get the viewer to watch the next ten seconds.”
Another might add: “Use contractions (you’re, not you are) to make your voiceovers sound more natural.”
Now, those insights are saved into a connected database and linked to the relevant step - in this case, Write script.
So, when I reach that same step in my workflow, those insights automatically appear. No messaging Dave to ask him how he does it. No asking ChatGPT for advice. No hunting around on the shared drive for that cheat sheet you downloaded last year.
The insights appear inside my workflow at the precise moment they’re needed.
Wow.
For the second time in as many emails, the implications floored me.
Just think of all the retros in which we’ve uncovered valuable learnings. All those project post-mortems in which we figured out what worked and what didn’t. All those insightful debriefs our talented colleagues are having.
What happens to all these learnings?
We might remember some. But if we’re honest, the vast majority is lost…
But this system captures it, and then surfaces it at the moment of need.Now, you may be thinking “yeah ok, that’s quite cool Pughie, but if our clients and employers can’t use Notion, what's the point?”
And that’s a fair objection.
But ultimately, what’s important here are the concepts, not the tech. Because once we can see the destination, we can figure out how to get there. And with the tech evolving, there are many ways to skin this cat.
So, sit tight - because we’re only just getting started.
Yours,
- Ant
