$11 WELL SPENT A SERVICE TO THE COMMUNITY
You’re one
more layer
away.*
Why do the hard work of aligning stakeholders when you can just buy another tool?
* From another layer.
Nick bought this domain during a webinar so a vendor couldn’t get there first. This is what happened next.
YOUR CONTEXT ARCHITECTURE
REV 001ENTERPRISE-READY. DEFINITION-PENDING.
“What do we mean by customer?”Sales and Finance still disagree.
† Meaning sold separately.
Easier than getting everyone in a room.
OKAY, THE ACTUAL POINT
Context won’t
procure itself.
Someone still has to get the stakeholders together, work through the disagreements and decide what things mean.
Agree who has the authority to decide. Record the definitions, decisions and exceptions. Make that knowledge easy to retrieve. Then choose the tools that help.
A LITTLE CONTEXT
For the actual work.
This site is a joke. If you’re serious about building a context layer, here are some people who actually know what they’re talking about. Check them out.
People worth following
- Juan SequedaKnowledge graphs & semantics
- Jessica TalismanInformation architecture & ontologies
- Anna BergevinData product management & context
- Juha KorpelaBusiness concepts & data modelling
- Vin VashishtaAI strategy & knowledge graphs
- Joe ReisPractical data modelling
Is there someone else who should be on this list? Let me know.
Inspired by Anna Bergevin’s “The Context Layer: Architecture, Not Another Tool” session with the Data & AI Product Management community.
“What a service to the community, Nick.”Anna, on the domain purchase. Definitely not a product endorsement.