Why AI Won’t Kill Consulting (But It Will Kill Busywork): Nick Tucker | Tim Jeffries & Jerwin Parker
Notion in PracticeShow Notes
In Episode 5 of Notion in Practice, Jerwin and Tim sit down with Nick Tucker. He is an experienced management consultant, psychologist and people leader, driven by a desire to make the world a better place to work.
Nick shares how he uses Notion as the operating system for his consulting practice: a “second brain” that captures context, keeps the admin tidy, and makes work easier to deliver with partners.
This is not a hype episode. It’s a practical look at where AI is genuinely creating leverage, what still needs human judgment, and why adoption remains the hard part. What we cover Nick’s background (strategy, culture change, organisational psychology) and how he discovered Notion Notion as a “second brain” that “keeps receipts”: admin + context + delivery Why AI challenges the traditional consulting leverage model (and what replaces it) The 4 workflow shifts: project management, meeting notes, pipeline/commercials, and IP management Using AI for feedback/coaching via custom rubrics (discovery calls) Adoption is still the hardest part: tools get deployed, but usage stays low AI as a thinking partner (mental models + frameworks like Pyramid Principle) What surprised Nick: inconsistency (“hungover graduate” days) What’s next: “get the reps in” and keep feeding context as the system grows
Top takeaways (from the conversation) AI changes the consulting advantage: The differentiator moves from producing repeatable “deck work” to using good judgment. The real skill is deciding what’s useful from endless AI output. Notion works best as an operating system (not another tool): A flexible “second brain” that keeps your delivery, context, and admin in one place, built around how you think and work. Four workflow upgrades drive leverage: Project management (single source of truth), meeting capture (searchable conversations), pipeline/commercial tracking (accountability), and IP management (drafting guides faster). Use AI for feedback and coaching, not just tasks: Call-review rubrics and automatic retros help people improve without the social friction of “I’ve got feedback for you.” Adoption is the real bottleneck: The tools can be there, but if people do not use them, nothing compounds. Systems that make work easier win adoption. Resources mentioned Nick Tucker on LinkedIn: https://au.linkedin.com/in/nick-tucker- Buoyant Partners (company): https://www.buoyant.partners/ HostsJerwin Parker Roberto: LinkedIn http://www.linkedin.com/in/jerwinparker Tim Jeffries: Instagram https://au.linkedin.com/in/timjeffries
AI call-review rubrics (concept): https://smoothopsconsulting.notion.site/AI-Thinking-Partner-Playbook-Setup-Guide-1c0149969f724589a840a541fa434a75?source=copy_link (AI Thinking Partner Playbook, Setup Guide) Pyramid Principle (framework mentioned)
More from Notion in Practice
Flight Centre Travel Group's Matt Upton explains how his automation team uses Notion, Notion Workers and Notion AI skills at enterprise scale, and why nothing gets automated until the process behind it is fixed. Matt is Head of Automation and Innovation for Flight Centre's Asia Pacific corporate brands, leading a team of around 30 across five brands from India and the Middle East to Japan, Australia and New Zealand. Inside a 12,500-person business, the work ranges from multi-step customer onboarding automations to five-minute tasks done 500 times a day. He joins Tim Jeffries and Jerwin Parker on Notion in Practice to walk through how his part of the business made Notion its single source of truth. Information used to be spread across Confluence, Azure DevOps, SharePoint, OneDrive and local files, and nothing joined up. Flight Centre's corporate technology teams now have roughly 1,000 Notion seats. "I tell people if it's not in Notion, it doesn't exist," Matt says, and that rule is what made the change stick. Who this is for Operations, automation and technology leaders fitting Notion, Workers and Notion AI into an existing enterprise stack, and smaller teams who want the same discipline without the headcount. Why can't you automate a bad process? Because automation speeds up whatever process it runs on. Matt's team won't automate anything until it has been through a continuous improvement pass. As Tim puts it, automating a bad process just makes the chaos go faster and the mess grow quicker. How did Notion take hold at Flight Centre? Microsoft Loop opened the door. Notion had been in the business for years with only a handful of real users, and once teams saw collaborative documents working in Loop, a few people pointed out that Notion already did this at scale. How does Matt's team sync Smartsheet and Azure DevOps with Notion? With Notion Workers, small pieces of code deployed to Notion. Matt has seven or eight Smartsheets plus Azure DevOps syncing into Notion databases this way, set up in a short conversation with a coding tool and left to run without babysitting. Most Workers do one plain job like this. How do you build a Notion Worker? Start with a brief. Tim gets clear on the problem with Notion AI, then hands the brief and the Worker docs to Claude Code. His Worker was deployed and working within an hour. Do you have to migrate everything into Notion? No. Smartsheet and Azure DevOps stay where they are as the data layer, Notion becomes the context and reporting layer on top, and Workers keep the two in sync. The episode also covers Notion as "the Switzerland of AI", connecting different models and tools. Three actionable takeaways Run a continuous improvement pass before you automate anything. Leave your system of record where it is and use Notion Workers to sync the data into Notion. Start every Worker with a brief from Notion AI, then point a coding tool at the brief and the Worker docs. Resources mentioned Tim's article "You already have a digital operating system": https://smoothopsconsulting.substack.com/p/you-already-have-a-digital-operating
AI doesn't run in a vacuum. It runs inside a world: the platforms your work lives on, the records that hold the truth, the rules about what happens next. Most AI disappointment isn't a model problem. It's that there was never a world built around it.
Tokens don't grow on trees. So what are you actually paying for when you pay for AI agents?
In Episode 9 of Notion in Practice, Tim Jeffries and Jerwin Parker tackle the question on every Notion power user's mind: what will custom agents actually cost and is it worth it?
What happens when a former lawyer becomes Head of Operations at a scaling startup and decides to build an entire ops function using Notion agents?