SECTION 02 / 19
Who should we ask? Stakeholders and users
When a software system is introduced it influences different types of users — from your own organisation, other organisations or end users, with different roles and profiles. All these users are called stakeholders. We must understand their requirements in a broad, holistic manner before designing.
EXAMPLE Amazon wants to develop a portal for sellers. Products which sellers list on the portal will be available for people to buy on Amazon.
THINK Who are potential tertiary users of the Seller Portal? Pause and write down your responses before reading further.
| Type | Meaning | Seller Portal example |
|---|---|---|
| Primary | Frequent users of the system | Independent sellers; sales team of consumer companies (e.g. electronics – mobiles, computers); independent authors and publishers |
| Secondary | Do not directly use the system; use it through an intermediary | Sales managers who periodically check sales numbers, profits and margins through their sales team |
| Tertiary | Do not use the software at all, but are affected by its introduction or influence its purchase | Logistics/shipping companies (deliver items to buyers); banks (timely transfer of money to sellers); buyers (what they buy depends on what sellers list) |