Glossary
Plain-English definitions of technical terms that business owners encounter when evaluating, buying, or managing software projects.
What Is Kanban
Definition Kanban is a workflow management method that visualises work on a board with columns representing stages, limiting work in progress to prevent bottlenecks. Why It Matters Kanban makes invisible work visible. When tasks exist in emails and heads, nobody knows what is blocked. A kanban board shows the entire workflow at a glance. Example A support team sees eight...
What Is a Keyword
Definition A keyword is a word or phrase that people type into a search engine when they are looking for something. In the context of SEO and digital marketing, keywords are the terms you want your website to appear for. “Accountant in Manchester,” “best CRM for small business,” and “how to fix a leaking tap” are all keywords. They can...
What Is a KPI
Definition KPI stands for Key Performance Indicator — it is a measurable value that tells you how effectively your business or team is progressing toward a specific objective. KPIs are not just any metric; they are the ones that matter most to your goals. Revenue growth rate, customer retention percentage, average project delivery time, and lead conversion rate are all...
About the Glossary
Why Plain Language Matters More Than Technical Fluency
Every software project involves terminology that business owners are expected to understand but rarely have reason to learn. Developers use terms like API, CI/CD, middleware, and bearer token as if everyone shares the same vocabulary — and when a client nods along without fully understanding, decisions get made on incomplete information. That gap between technical language and business understanding is where the most expensive mistakes happen: approving architectures you cannot evaluate, signing off on testing strategies you cannot verify, and accepting timelines based on concepts you have not had properly explained.
This glossary exists to close that gap. Each entry provides a plain-English definition, an explanation of why the term matters to your business, and a concrete example of the concept in action. These are not textbook definitions written for computer science students. They are practical explanations for the person who needs to make decisions about software without becoming a developer in the process.
We built this glossary from the questions our clients actually ask — in discovery calls, during project reviews, and in Slack threads where someone finally admits they are not sure what a term means. The entries reflect what business owners genuinely need to understand, not what a technical writer thinks is important. Across hundreds of client engagements, we have found that the single biggest predictor of a smooth project is a client who understands enough vocabulary to ask the right questions. Not to write the code — just to evaluate the answers they are given.
The definitions here deliberately link to deeper content elsewhere on the site. If a glossary entry sparks a question about how we implement something, the Knowledge Center, Services, and Systems sections have the full picture. The glossary is the starting point, not the destination.
Need a Term Explained?
If you have come across a term we have not covered yet, let us know and we will add it.