AICHE +Confluence Integration

The short answer: open a Confluence page in edit mode, click where you want text, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak for 30-60 seconds, and AICHE inserts the transcribed text at your cursor position.

Confluence is where institutional knowledge goes to live or die. When documentation is current, teams operate independently. New hires onboard faster. Runbooks prevent 3am panic. Architecture decisions have recorded rationale. When documentation is stale, teams waste hours in meetings asking questions that should have been answered by a wiki page.

The reason Confluence pages go stale is not that people do not care about documentation. It is that updating a page takes 15-20 minutes of focused typing, and that never feels urgent enough to prioritize over feature work or bug fixes. Voice reduces the friction enough to change the behavior. If updating a runbook takes 3 minutes of speaking instead of 15 minutes of typing, it actually happens when the information is fresh.

1. Open Confluence in your browser and navigate to the page you want to edit.
2. Click the Edit button (pencil icon) or press E to enter edit mode.
3. Position your cursor in the content area - inside a text block, below a heading, or in a new section.
4. Press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux) to start recording.
5. Speak your content naturally - procedure steps, decisions, observations, or explanations.
6. Press the hotkey again. AICHE transcribes and inserts the text.
7. Apply Confluence formatting: add headings, use the Expand macro for long sections, insert Jira links, or apply the Info/Warning/Note panels.

Heads-up: Dictate content first, then apply Confluence formatting and macros. Separating writing from formatting makes both tasks faster. Speak the substance, then dress it up with Confluence's toolbar.

Technical Runbooks and Playbooks

Writing Incident Response Procedures

Runbooks are the most valuable and most neglected pages in any Confluence space. They describe what to do when something breaks at 3am, and they need to be accurate, detailed, and current.

Open your team's runbook page, click Edit, and dictate the procedure. Walk through each step as if you are talking to a junior engineer who has never handled this incident type before. Say "first, check the CloudWatch dashboard for the API service and look at the error rate graph for the last 30 minutes. If error rate exceeds 5%, proceed to step 2. If it is below 5%, this alert may be a transient spike and you should monitor for 10 minutes before escalating." Continue through diagnosis, mitigation, resolution, and post-incident steps.

Spoken procedures tend to include the small details that experienced engineers skip when typing - how to find the right dashboard, what the threshold actually means, when to escalate versus when to wait. These details are exactly what junior engineers need during an incident.

Keeping Runbooks Current

The hardest part of runbooks is keeping them accurate as systems change. Voice makes incremental updates practical. After a deployment changes infrastructure, open the affected runbook, navigate to the outdated section, press your hotkey, and dictate the update. A 30-second update beats a 15-minute rewrite, and the runbook stays accurate.

Meeting Notes and Decision Records

Capturing Meeting Outcomes

After a meeting, open the Confluence page for that meeting (or create one from a template). Press ⌃+⌥+R and dictate the key points while they are fresh: what was discussed, what was decided, who owns each action item, and what the next steps are. Enable Content Organization to have your spoken summary structured into clear paragraphs.

The value of dictated meeting notes is immediacy. The meeting ends, you dictate for 3 minutes, and the notes are published before attendees reach their next meeting. Compare this to typed notes that sit in a draft for two days and get published when nobody remembers the context.

Architecture Decision Records

When your team makes a technical decision (choosing a database, selecting a deployment strategy, defining an API contract), create an ADR page in Confluence. Dictate the context: what problem you faced. Dictate the options: what alternatives you considered. Dictate the decision: what you chose and why. Dictate the consequences: what trade-offs you accepted.

ADRs are the single best way to prevent "why did we build it this way" questions months later. Voice makes them feasible because dictating a 500-word ADR takes 3 minutes instead of 20.

Onboarding and Knowledge Transfer

New Hire Documentation

Your team's onboarding documentation determines how quickly new hires become productive. Open the onboarding page, and dictate environment setup instructions, codebase overview, team conventions, and common pitfalls. Speak as if you are sitting next to the new hire walking them through their first day.

Update these pages whenever a new hire reports confusion. After answering their question verbally, press your hotkey and dictate the answer into the Confluence page so the next new hire finds it there instead of asking again.

Process Documentation

Every team has processes that live in tribal knowledge - how to cut a release, how to handle a customer escalation, how to set up a test environment. These processes should be Confluence pages, and voice makes writing them practical. The next time you perform a process, open a new Confluence page, and dictate each step as you do it. The result is a first-person walkthrough that captures the procedure with enough detail to actually follow.

Confluence-Specific Tips

• Jira integration. After dictating a page, use Confluence's Jira macro to link related tickets inline. The dictated context plus linked Jira tickets creates a complete picture.
• Page templates. Start from a Confluence template (Meeting Notes, Decision, How-To Article) and dictate into each section. Templates provide structure; voice provides content.
• Comment collaboration. When a colleague's Confluence page needs updating, add an inline comment with your correction instead of editing their page directly. Press the hotkey and dictate the suggested update. They review and apply it.
• Space-level descriptions. Every Confluence space has a homepage description. Dictate a clear overview of what the space covers and who should use it. This helps new team members navigate the wiki.

The pro-tip: When documenting processes with multiple steps, enable Content Organization in AICHE settings. Your spoken explanation gets structured into clear paragraphs that map to Confluence's numbered list format. Add numbered list formatting after dictation, and you have a clean procedural document.

Result: Runbooks that get updated after every infrastructure change. Meeting notes published within minutes of the meeting ending. Architecture decisions recorded with full context and trade-off analysis. The documentation culture that teams aspire to, made practical by reducing the effort per page.

Do this now: Open a Confluence page that is outdated, click Edit, press your hotkey, and dictate the corrections based on what you know has changed since it was last updated.