Instruments,not a product line.

Guardian AI, PromptForge, Dark Pattern Detector, the Scrum Toolkit — four privacy-first browser tools that exist to make the other five pillars stick in day-to-day work. All free public beta. You don't buy them; an engagement rolls one out.

Installing PromptForge doesn't make structured prompting a habit. Loading Guardian AI doesn't create AI oversight. The tool is the easy part — the value is in the fit, the rollout, and the governance around it. That's the work this pillar does.

What the tools are

• Guardian AI — enforces AI-usage policy at the browser, and doubles as a critical-thinking checkpoint: did a human actually think about this before sending it?
• PromptForge — puts structured prompting frameworks into everyday practice.
• Dark Pattern Detector — a working example of AI used for consumer protection: flags manipulative UX on the pages you visit.
• Scrum Toolkit — runs every ceremony by the 2020 Scrum Guide in a single page.

All four are free public beta. They're instruments of the practice, not a separate product.

Three things to
get right

Fit without rollout is shelfware. Rollout without governance is an ungoverned data flow at scale.

What good looks like

• Each tool addresses a named problem here — not "this looks useful".
• Tooling has one owner who decides what's rolled out, configures it, and fields questions.
• The tool slots into a workflow people already have — it isn't a new habit nobody asked for.
• The intended users have tried the free beta and fed back before any rollout.
• "Adopt a tool" is tied to an outcome you'd notice — not an install count.

Deployed,
not just shared

• Browser policy allows extensions, and there's a managed way to deploy them.
• There's real onboarding — "what it does, how we use it" — not a link in a channel.
• Adoption is measured — who's using it, is it helping — not assumed after launch.
• Users have a channel to report friction that reaches someone who can act.
• If the champion leaves, tooling survives — config documented, more than one person across it.

Known,
not assumed

• You know each tool's data flow — what runs locally in the browser vs what calls an API.
• Any API key is owned, scoped and rotated — not pasted from a personal account.
• The tools went through the same privacy and security review as other software.
• The tools are explicitly covered by your AI-usage policy — or the policy gets written.

• Fit without rollout — the right tool, installed by three people, quietly abandoned.
• Rollout without governance — a whole team on a tool whose data flow nobody has checked.
• Governance without fit — a locked-down, reviewed tool that solves a problem you don't have.

Find the weak one and reinforce it first. That's the engagement in a sentence.

Where tooling
goes nowhere

• Shiny-object install — adopted because it's clever, not because it solves a named problem.
• Link-and-leave — dropped in a channel, no onboarding, no follow-up.
• Nobody owns it — so nobody configures it, answers questions, or notices it died.
• Personal keys — a tool running on someone's private API account, unmanaged.
• Off the governance radar — never reviewed like other software, invisible to the AI policy.

The readiness check

• 14 questions — about four minutes, scored in the browser.
• A score for fit, rollout and governance — and a combined grade from Curious to Embedded.
• A concrete first move for each area.
• Take it before the first conversation: jtctech.co.za/assess-tools

It's tool-agnostic — it measures whether any tool would land here, before you pick one.

Fit → roll out → govern

Where it starts

What you keep

• The four tools are made in-house — the rollout advice comes from running them ourselves, privacy-first.
• Led by Jon Boyle, who has lived the AI and Agile adoption curve inside a real team at scale.
• Tools sell as rollout within an engagement, not licences — so the incentive is adoption that sticks, not seats.

Start with theweak one.

Take the readiness check, then a 30-minute conversation about which tool to roll out first — and what has to be true around it.

hello@jtctech.co.za · jtctech.co.za · Built in South Africa 🇿🇦