Start with the work itself
The need for a web application often begins with a specific task: information is entered repeatedly, a request passes through too many people or data is scattered across different tools.
Before choosing technology, map the current workflow. Who receives the information, who processes it and where is the result stored? A concrete example makes bottlenecks easier to discuss.
Review the tools you already have
An existing product may work well when your process is common and requires little customisation. Check whether improving how you use your current tools could solve the problem first.
A custom application becomes worth considering when you need a specialised workflow, particular access rules or data connections that existing tools cannot reasonably support.
Keep the first scope focused
Rather than putting every business activity into the first release, choose one process with a clear start, finish and group of users.
- Who will use it each day?
- What are the inputs and expected outputs?
- What needs to be checked before delivery?
- Who owns the data and provides support after launch?
Plan for ongoing operation
An application needs hosting, backups, updates and support as well as design and development. Agreeing responsibilities and an incident process early makes the investment easier to plan.
Have a workflow you want to improve? Share it with Viral Buzz Vietnam. We can help clarify the problem before choosing a solution.
