Addressing Blockers to Effective Knowledge Management: Q&A Highlights and Next Steps

[#1]

Thanks to everyone who joined this week’s webinar, Addressing Blockers to Effective Knowledge Management.

We received a lot of great questions – so we’ve pulled them together here, including answers to the ones we didn’t get to live.

Have another question? Drop it in the comments below 💬

Quick intro & recap

I’m Michael Rowe, Principal in Atlassian’s Advisory Services, and I’ve spent my career helping organizations unlock the full potential of their teams through better knowledge management.

This session covered practical patterns and real-world stories from my work with teams across industries, focusing on how to:

• 📝 Capture and organize tacit know-how

• ⏩ Shift to open-by-default and async sharing

• 🤖 Make knowledge discoverable and AI-ready

• 🎯 Connect knowledge to work and goals for faster, better outcomes

Q&A highlights and extended answers ⬇️

---

1) How do we motivate teams to capture ‘obvious’ or ‘easy’ tasks?

Automate where possible and keep process lightweight and in‑flow:

• Make capture visible in workflows: include capture in Definition of done

• Reduce friction: use Loom and meeting minute captures

• Reinforce: recognize teams and individuals

💡Pro tip: Share search analytics in retros to show how many people used a page. Visibility creates intrinsic motivation.

---

2) What are the first three signs knowledge management is failing, even if it ‘feels’ fine?

• 1. Decisions disappear into meetings – recurring “what did we decide?” pings; no durable decision log.

• 2. Duplicate effort – multiple teams building similar docs/processes; low linking to existing content.

• 3. Findability drops – search‑to‑action ratio declines; more Slack pings for basics; growing “where is X?” time.

---

3) We’re going to scale fast-what should we setup early to avoid rework?

• 🧭 Lightweight information architecture: a small set of top‑level spaces aligned to domains (e.g., Product, GTM, Ops) with a simple page taxonomy.

• 👥 Ownership by design: name Knowledge Champions per domain (part‑time), plus a central enablement owner to run hygiene rituals.

• 📘 Templates and decision logs: standardize decision pages and meeting notes so scale doesn’t equal chaos.

---

4) Is there hard evidence that knowledge management impacts revenue, margin, or outcomes?

Shift measurement from content volume to value signals:

• Time‑to‑competency for new roles goes down; first‑call resolution and deal cycle time improve.

• Reuse rate rises: existing assets are applied to new projects; fewer bespoke docs.

These improvements reduce the cost of sale/service and increase productivity – tie them to OKRs for visibility.

---

5) How do we measure whether search time is actually going down?

• Search analytics: percent of searches leading to a click and resolved action (search‑to‑action).

• Pulse surveys: time‑to‑information for common tasks; trend this each sprint.

• Signal reduction: fewer basic “Slack‑pings” and fewer status‑only meetings.

---

6) How do we avoid a vague, multi‑year ‘System of Work’ transformation?

Use thin slices:

Pick one friction‑heavy workflow (onboarding, incident response), define a single success metric, apply knowledge management practices, measure, and repeat. Small, testable changes prove value and build momentum.

😎 Also, this feels like a good opportunity to invite you to join my next session next week, Unleashing Collective Knowledge for AI Discovery, to learn how effective content management can empower AI to surface valuable insights from your team’s collective knowledge. We’ll cover practical strategies and share a 30/60/90-day action plan.

---

7) Who owns taxonomy, lifecycle, and archiving-and how do we keep it funded?

Use federated governance:

Each function appoints a Knowledge Champion (5% role) responsible for accuracy; central enablement provides tooling, guidance, and automation (e.g., stale‑page workflows). Make hygiene a recurring ritual, not a one-off clean-up.

---

8) How do we stop creating yet another content graveyard?

Integrate knowledge with work:

Link pages in issues, reference runbooks in queues, and standardize labels. Use verification states and stale‑content alerts to keep content alive-and deprecate confidently when it isn’t. 🧹

---

9) How do we keep AI from amplifying chaos?

• Index only verified sources; exclude personal spaces and low‑signal areas.

• Human‑in‑the‑loop reviews for AI summaries; clear prompts and source controls.

• Automated lifecycle rules: archive or renew on schedule; owners get nudges before content stales.

• AI Governance; this will help feed into a Service Module.

---

10) How do we balance openness with compliance and risk?

Use permissioned transparency:

Keep sensitive data in controlled spaces, but publish process and lessons learned broadly. Aim for maximum learning with appropriate safeguards.

---

Recommended practices you can start this week

✅ Adopt a decision log template and link it from meeting notes.

✅ Create a single “Start here” page per domain with top links and owners.

✅ Turn on stale‑page reminders and set review cadences per space.

---

🚀 Keep learning and take action

Explore more practices:

• 🔗 Explore the System of Work to connect teams, tools, and practices for flow and outcomes.

• 📄 Run a page‑led meeting to make decisions discoverable and durable.

• 🗓️ Attend my next session: Join me next week for Unleashing Collective Knowledge for AI Discovery, tand learn how effective content management can empower AI to surface valuable insights from your team’s collective knowledge. We’ll cover practical strategies and share a 30/60/90-day action plan. Register here.

---

 ❓Questions we missed or want us to dive deeper? Drop them in the comments!