Who Owns Your AI Transformation?
IT, Marketing, and Operations can all claim ownership of your AI strategy. Committees claim nothing. The right owner is defined by what they can see, connect, and serve.
Your Team Doesn’t Understand Their Jobs (And That’s About to Matter)
The gap between knowing a job and understanding it has been invisible for decades. AI is about to make it the most important distinction on your team.
The Knowledge Management Revolution You Didn’t See Coming: 3 Skills Your Team Needs Now
AI hasn't solved the decades-old knowledge management problem. It's just changed which skills matter. Learn why capturing organizational knowledge is still the hardest challenge, and discover the three critical capabilities your team needs to succeed in the AI era.
Capturing Knowledge and Making It Findable
If the right document, report, presentation is difficult to locate, and people can't find it to use it - it might as well not exist. This article looks at multiple ways to overcome this challenge to facilitate corporate innovation.
Corporate Innovation and the Hierarchy of Information Needs
Master the hierarchy of information requirements to unleash corporate innovation, with insights into problem-solving and the importance of knowledge management.
Capturing Knowledge: A Critical Requirement for Corporate Innovation
Drilling into the important role of capturing knowledge in promoting corporate innovation, highlighting the importance of creation & curation, sharing & collaboration, and impactful use.
Unleashing Corporate Innovation: Identifying the Constraints
Corporate innovation struggles, and not from a lack of ideas or capital. More often, the constraints are time and attention.
Navigating Buzzword Overload: Complexity
Complexity means different things to different people in different conversations. Are we trying to simplify a process? Complexity is bad. Understand a supply chain? Complexity is good. Don't buzzword your initiatives with "complexity" until you get a wee bit more specific.
A Hierarchy of Information Requirements
It's a common problem statement - 'I don't have enough information to (run my business unit, manage this process, identify opportunities, etc.)'. The solution designer, when faced with a question like this, starts with a little detective work; the problem is too broadly stated.
Technical Debt and the Cost/Benefit of Knowledge Retention
A rather rigorous, Financial-sounding title for a high-concept line of thought ... Thanks to Jeff Atwood at Coding Horror, for calling my attention to this article by Martin Fowler on Technical Debt: Technical Debt is a wonderful metaphor developed by Ward Cunningham to help us think about this problem. In this metaphor, doing things the quick and dirty way sets us up with a technical debt, which is similar to a financial debt. Like a financial debt, the technical debt incurs…