When a website is the starting point
A website usually helps an audience explore information and take an action, such as making an enquiry or browsing a product catalogue. Content structure and clear journeys are central to the project.
- Explain your services and experience
- Publish information your team can update
- Help visitors enquire, book or buy
When a web application is the starting point
A web application supports tasks involving records, roles and changing states. Consider an application when people need to return to a system to manage work.
- Assign and follow up enquiries
- Review requests through approval stages
- Manage operational records and reporting
When the two need to connect
A public website can collect an enquiry that enters an internal workflow. Define the boundary between the public journey and the team workflow before choosing how to connect them. An integration may be more appropriate than rebuilding an existing tool.
- Where does information enter?
- Which system owns each record?
- Who needs access, and what should happen next?
Choose by the work, not the label
Features such as login or payments do not settle the choice on their own. Discuss the users, information, exceptions and support needs. The right scope may combine a content-managed website with a small custom tool.
- Map one complete user journey
- Identify existing tools worth keeping
- Discuss maintenance and content ownership
Put it into practice.
Bring a typical customer journey and a typical team task to the discussion. They reveal more than a preferred platform name.
Discuss Your Project