Has anyone here worked with a context graph of work?
I've seen this term a few times lately and I'm still trying to understand what it actually means in practice.
It first made me think of IBM's work around knowledge graphs and connecting enterprise data. Then I came across Skan AI using “Context Graph of Work” for something a bit more specific: connecting the people, systems, documents, decisions, and exceptions involved in getting work done. I can see the appeal. Most process maps look clean, but the real workflow usually involves email, spreadsheets, Teams, manual handoffs, and a few steps nobody bothered to document. What I'm not clear on is whether this is genuinely different from a good process model or knowledge graph, or just another way of packaging the same idea.
Has anyone seen it used in a real project?