Still Thinking audits the editorial decisions made before anyone opens a document. Most teams don't have a writing problem. They have a thinking problem that shows up in the writing, and feedback on the writing won't fix it.
These are not writing problems. They are thinking problems. The distinction matters because fixing the writing does not fix the thinking. Most content feedback addresses the symptom and leaves the root cause completely untouched.
Here is what the audit finds most often:
The same thinking problem shows up differently depending on where you sit.
Your team's output went up and the rankings didn't follow. You're giving the same feedback every week and watching it not stick. The feedback isn't wrong. It just isn't naming the right thing.
Your content used to be a differentiator. Now it reads like everyone else's, and you can feel the brand softening without being able to name where it slipped. The team is producing. The voice is fading.
Search performance is dropping. Reader trust is harder to hold. The team can't name why their work isn't landing the way it used to. The content is the product, and the product is getting quieter.
Three years into the AI shift, the pattern is consistent across studies. Teams are fatigued. The thinking is weaker. The outcomes are measurable.
Every piece is scored against a four-part rubric. Every writer gets a named failure pattern. The team gets a map of where the thinking breaks down and the three structural fixes that will move the work fastest.
| Dimension | Writer A | Writer B | Writer C |
|---|---|---|---|
| Angle construction | 4.2 | 7.8 | 6.1 |
| Audience thinking | 3.8 | 8.2 | 4.4 |
| Evidence usage | 5.5 | 7.4 | 3.9 |
| Originality | 3.1 | 6.6 | 2.8 |
For a 6-writer team at the founding rate.
Most editorial feedback fails the same way. Make it sharper. Add more depth. This feels generic. The writer nods, can't act on it, and submits the same shape of piece next week. Nothing changes because nothing got named.
I built this audit on a real 9-writer team because I needed it. Not a framework I invented to sell. The actual review system I run every week. The taxonomy came from the patterns I kept seeing. The rubric came from the conversations that weren't working. The fixes came from what actually moved the work.
I've spent eight years leading content functions across B2B SaaS, automotive, GovTech, healthcare, blockchain, and digital transformation. For audiences in North America, Europe, and the MENA region. Including government modernization programs in the UAE and Saudi Arabia. The thinking failures don't care what industry you're in. They repeat everywhere.
This is the system I use on my own team. It is the system I will run on yours.
The eight-page document is the actual review system behind the audit. The taxonomy, the rubric, and a worked example with one real before-and-after. If you want to understand what thinking failures look like in practice before spending anything, read this first.
The framework shows you how the system works. The audit reveals where your team's thinking breaks down and what to do about it.
The taxonomy. The rubric. The worked example. This is the actual system. Read it and you will immediately be able to apply it to your team's work.
The audit is a real diagnostic on real work. Begin one and I'll review your submission personally within 24 hours. Not ready yet? Start with the free framework and run a version on your own team.