Body of Knowledge · Glossary
Core versus context
Build what differentiates the business in its customers' eyes (core), and buy or adopt the commodity (context) so engineers are free for differentiating work. Core means differentiating, which is a different thing from important. Email is important and almost never core.
Where the standard develops it
- SV-4Engineering economicsHeadcount, budget, cost of delivery, vendors, and build/buy/AI decisions.
Related terms
- Build, buy, or AI service
- The three-way capability decision (build it, buy a product, or adopt an AI service), with each option weighed by the same questions: is this core, what is the lifetime cost, and where are we left if the provider or partner changes course?
- Charter
- The explicit statement of what a team or department owns.
- Sunk cost
- What has already been spent, which argues for nothing in a decision about the future.
- Total cost of ownership
- The full lifetime cost of a capability, meaning build cost plus maintenance forever, or purchase price plus integration, lock-in and exit.
Cite this definition
Chicago, BibTeX and licence →Engineering Management Academy. (2026). Core versus context. In Engineering Management Academy Body of Knowledge (Version 3.1, GLO.core-versus-context). https://www.engineeringmanagement.academy/body-of-knowledge/glossary/core-versus-context