Business management
Business management
This domain tests how web work is scoped, justified, governed, and measured. WP-C candidates should connect requests to business outcomes, define acceptance criteria, control scope, and account for total cost rather than launch cost alone.
Core rules
- Write requirements with acceptance criteria and a named owner; separate must-have from nice-to-have.
- Use change control: new scope means a documented impact on cost, schedule, and risk.
- Budget total cost of ownership: build, hosting, licenses, maintenance, content operations, and accessibility remediation.
- Define success metrics and guardrails before launch; establish a baseline.
- In vendor work, clarify SLA, responsibilities, and escalation paths.
- Treat privacy, consent, and accessibility as business risks, not only technical tasks.
Worked example
A stakeholder asks for a new promotional banner. A weak response is an immediate estimate. A stronger response states the business goal, proposes a measurable hypothesis, and costs the work: design and build effort, ongoing content maintenance, analytics instrumentation, and testing. If the expected conversion lift is uncertain, run a limited test rather than a full rollout. Reasoning: the decision becomes comparable to alternatives, and the team commits to a metric and a guardrail instead of an opinion.
Traps
- Reporting page views as success without a business outcome.
- No baseline, so improvement cannot be proven.
- Gold-plating features outside the agreed scope.
- Promising fixed dates without contingency for review and remediation.
- Ignoring ongoing maintenance and content ownership after launch.