Sign in with your Iconic email.
Everything the team logged this week, drawn straight from their own entries.
One champion per division learns to solve real Iconic problems with Claude — building on the same in-house stack (Claude Code · GitHub · Railway) that already put the BBFA Tracker into production. The program owner coaches every spoke.
Approved and being built — and only those. A Claude skill is different work, so it goes in the Skill Jar beside the cards rather than onto the board — but it still carries an estimate and a savings forecast, so it counts on the Cost page exactly like an app. Everything else with a champion assigned to it lives here as a live build card: who owns it, their task, target start and completion dates, and the current build stage. It arrives automatically when it is approved on the Opportunities tab, whether it came from the TELUS assessment or from someone's submitted idea, and it leaves that queue at the same moment.
Tickets raised to IT for the AI program — access, tools, hardware, fixes. Raise one with the button below.
UNDER CONSTRUCTION
These screens are still being built, so they are password-protected for now. Enter the Cost Tracking password to continue.
Three questions, kept apart because they have different audiences and different answers: is the program worth it, is each build on budget, and where is capacity going. Every figure below is a filter over one ledger of money events — click any number to see the rows behind it.
Plan capacity month by month. This auto-captures the hours already logged across every project: Hours Saved by Position becomes a Worker (capacity freed, +, to add to their day-job) and Workers & Labour build hours become an AI Champion (−, removed from their day-job scope). You can also add rows manually below. The net, by person and position, shows month by month where capacity is opening up or getting tight. 1 FTE ≈ 173 hrs/month.
Every QMS document logged across all projects, consolidated here with its approval tick-off: ① Champion uploaded procedure → ② Process manager revised → ③ Approved & in place. Documents are attached on each project's "Updates to QMS" card.
Free training from Anthropic, organized by product the way Claude Academy does it: what each product is, then how to learn it. Each patch shows how long it takes.
Claude Academy is Anthropic's free training site. Iconic is on the Claude Team plan, so courses about the API, Enterprise rollout and cloud platforms are left out here.
Claude Academy ↗ Browse everything ↗Chat with Claude to think a problem through, check a draft, or make sense of data. Start here.
What Claude can do, your first prompt, and working with your own files.
Open ↗Everyday work: prompting, projects, artifacts, skills and connected tools.
Open ↗Keep related chats, files and instructions together.
Open ↗When to use Haiku, Sonnet, Opus or Fable.
Open ↗Link Claude to the apps you already use.
Open ↗Give Claude a multi-step task, step away, and come back to finished work. Anthropic is folding Cowork into Claude itself; what these teach still applies.
The setup to do before your first task.
Open ↗Hand Claude a real piece of work and steer it.
Open ↗Workspaces, context, task loops, and plugins for research, documents and browser tasks.
Open ↗Set it up for your own work or your team.
Open ↗Change what a plugin does to fit how you work.
Open ↗Have Claude run a task on a schedule, such as a weekly digest.
Open ↗What to watch for when Claude works on your files and the web.
Open ↗A live build-along: connectors, skills, permissions and a scheduled digest.
Open ↗Build software and tools with Claude, from plan to shipped change, like the builds on the Opportunities board. Start with Your first day.
Install, sign in, and ship your first change.
Open ↗What Claude Code is, how it works, and the core workflows.
Open ↗CLAUDE.md and prompting habits: the highest-value setup step.
Open ↗Run long, hands-off sessions you can trust: steer, configure, automate, verify.
Open ↗Build, share and troubleshoot Skills that Claude applies automatically.
Open ↗Delegate to sub-agents and keep the main conversation focused.
Open ↗Best practices from people who use it every day.
Open ↗Hands-on: install, fix a live bug, teach it your codebase.
Open ↗Context, permissions and hooks, and running several agents.
Open ↗Own the whole arc, from problem to shipped solution.
Open ↗How AI works and how to work with it well, whichever product you use.
Links checked on 25 Sep 2026 against academy.claude.com, code.claude.com and support.claude.com. Organized by product as on Claude Academy; Platform (the developer API) and Claude Tag (for Slack) are left out. Anything new appears under Browse everything.
The race to connect every business system to one central place, the first step to powering AI with Iconic's own data. Put a date, funding and a name on each system, drag its runner as it moves, and click its logo for the details and the plan.
Every opportunity on one line, by quarter. Each colour is a stage of the framework, from the date that stage starts to the date the next one does; the flag is the go-live date. Set the dates inside each card, on each stage. Click a line to open its card.
Testing lists the apps people can try right now, before they are finished. Completed lists every app live in production. A build appears here by itself from the addresses on Track the Build: a Testing address puts it under Testing; once it is complete with a Production address it moves to Completed. Add one by hand only if it was never built through this tracker. Click an app's line to open its page: what it is, how to use it, screenshots and comments.
Every idea comes in here and lands on 1. Idea. The IT business partner adds an assessment, then the assessment panel takes it through the decision tree inside 2. Ideation. From there it is always in one of the six framework buckets.
Drag a card to move it between buckets; click it to open it. Click a bucket's heading to read what that stage requires. The ten-business-day clock runs only in Ideation, from submission to a recorded decision.
Three ways an idea gets in. Type it straight in, download the Word form and fill it offline, or attach the document Brainstorm produced for you — all three land in the same queue.
Nobody contacts a vendor before Initiate. The exec gate into Initiate is what gives a person authority to write detailed requirements and to approach suppliers. A card in Idea or Ideation carries no such permission.
Every row that adds up to it
Fully burdened cost by position — the only source of an hourly rate in this app
Ask for a change to the tracker or a new feature. It goes straight to the tracker's admin.
Changes and features the team has asked for. Newest first.
Who can sign in to the tracker
Choose how you want to submit it. All three land in the same place.
Attach the document Brainstorm produced, or the Word form you filled in offline.
Brainstorm is the Copilot agent people use to work an idea up before it reaches this page. When they are happy with it, it writes the Opportunity Definition for them. Attach that document here and the fields fill themselves. The whole document is kept, and anything Brainstorm added beyond the form can be read inside the card.
Findings from the TELUS assessment, re-entered for assessment under this framework.
The TELUS assessment was carried out before this framework was adopted, and its findings may no longer reflect how the work is done. A finding pulled here enters at 2. Ideation with no checks ticked. The earlier assessment is not carried forward: the IT business partner assesses it again, and the panel decides again.
Builds that have become one project can be stacked, so the board shows them as one multi-project card. Nothing is merged: each keeps its own card, build, hours, estimate and Cost-page figures, and any card can be taken back out of the stack. Stacked cards move together, into this card's column.
What it is, how its data moves, what it costs, and the plan to connect it.
Opportunity Definition — the business case for a new idea
Raised to Adam — IT Technical Administrator
Every save is kept, so any mistake can be rolled back.
They appear on the org chart with their own onboarding status, and become assignable to projects.
Step 2 of 2 — who gets time back, and how much