Understand projects, products and budgets
Project vocabulary helps decide who does what, with which outcome and verification. Separate need, proposed solution and approval responsibility. A budget or deadline makes sense only with explicit scope and dependencies.
38 concepts to explore with definitions and practical advice.
Search the full glossary
A reading path
1. Define the outcome
Describe audience, problem and expected deliverable. A blocking requirement should be distinguishable from a preference or option.
- Website brief
Planning document connecting goals, audiences, pages, content, functions, constraints and acceptance criteria for a website project.
- Hard requirement
Essential condition set before a comparison; an option that fails it leaves the shortlist even if it performs well on other criteria.
- Acceptance criteria
Specific, testable conditions used to decide whether a delivered feature or page meets the agreed need.
2. Compare approaches
Examine required functions, data to maintain and exit conditions. A minimum version tests a hypothesis without hiding journey limitations.
- MVP
Minimum Viable Product: first version useful enough to test with real users and guide improvements.
- Benchmark
Structured comparison of solutions, performance or practices to identify gaps and improvements.
- Exit cost
Work and expense needed to recover data, replace a supplier, transfer access and continue a service without undue disruption.
3. Track decisions
Identify expected inputs, enquiry owner and approval points. Scope changes should be resolved before retaining the same commitments.
- Enquiry owner
Person or team responsible for following an enquiry, obtaining needed details, replying and recording why it is closed.
- Response time commitment
Stated period between receipt of an enquiry and a useful first reply. It needs a defined starting point, treatment of non-working periods and scope of requests.
- QA
Quality Assurance: organised verification process intended to prevent defects and confirm that a product meets expectations.
Useful distinctions
Acceptance criteria / SLA
Acceptance criteria describe a deliverable outcome and the test accepting it. An SLA defines service-level commitments within a context. They concern different situations and periods.
Starting price / Exit cost
A starting price does not describe every option or upkeep. Exit cost concerns recovery and transfer of data or service. Compare equivalent scope before drawing conclusions.
Use the vocabulary to make a decision

Situation
Two proposals look different while answering the same brief.
Before deciding
Compare deliverables, responsibilities, migrated data, upkeep and included tests. Price differences can reflect different scope.
A concrete check
Ask a specific question about each non-comparable item and retain the answer with the proposal.
Compare the same scope over the same duration
One proposal may include content migration, maintenance or testing while another prices them separately. Align the scope before comparing amounts.
On a narrow screen, scroll the table horizontally to read all three columns.
| Observed signal | What to check | What it means |
|---|---|---|
| The initial price is lower | Identify recurring costs and excluded work. | The starting price does not describe cost over time. |
| Testing is promised without criteria | Ask for journeys, devices and expected results. | An observable criterion makes the deliverable verifiable. |
| A new request arrives after approval | Clarify its effect on the deliverable, schedule and cost. | The change may require a scope decision. |
Next step : List non-comparable items and request a precise answer for each before choosing.
Technical reference : W3C WAI — Planning and managing. The scenarios and numerical examples above are educational, not measurements of this website.
A published page is not an acceptance report
Fictional teaching case. Open each interpretation to examine its scope; there is no score or professional assessment.
- Criterion agreed
- Result observed
- Decision assigned
A new section is accessible on a demonstration website. The project also planned to check keyboard use, links and the confirmation message.
What still needs to be distinguished?
A useful next step : Separate publication, completed checks and validation decisions. Project vocabulary should state who records outcomes and who decides the next step.
All concepts in this topic
Links open the full definition on its alphabet page. Acronyms and synonyms remain searchable in the main glossary.
- Acceptance criteria
- AI readiness
- Automation
- B2B
- B2C
- Benchmark
- Booking capacity
- Booking slot
- Checkout journey
- Comparable criterion
- CRM
- Double booking
- E-commerce
- Enquiry acknowledgement
- Enquiry owner
- Exceptional opening hours
- Exit cost
- Hard requirement
- Kanban
- Magento
- Migration
- MVP
- Prelaunch checklist
- Price effective date
- Product availability
- Product difference
- Product page
- Product variant
- QA
- Response time commitment
- ROI
- SLA
- Starting price
- Vacancy status
- Web sustainability
- Website brief
- Website job opening
- Yield management
Frequently asked questions
Must the whole project be detailed before the first discussion?
Present need, existing site, deadline and known constraints. Uncertain items can become questions to resolve rather than implied commitments.
Does checking a task accept the deliverable?
Performing a task and accepting its result are distinct. Check the agreed criterion with intended data and context, then record remaining limitations.
Primary reference documents
These documents explain technical concepts. Reading paths and examples are editorial methods to adapt to your project.