
Define What the Work Is
The first thing you’ll want to consider is the scope of work. Whilst the buyer may have an idea of what they want, the real question should start with asking ‘what’ is going on. Why is the Austin founder looking for a new agency? What is an Austin founder currently doing when comparing agencies? How is the Austin founder solving this issue? This is your real scope of work. An example of this could be that the founder has received 3 completely different quotes for what appears to be the same app. When looking into app development company in austin, think about what the real business problem is.
Before asking for a quote, ask what success looks like. In the first conversation, try to separate out from the tool. Ask founders/businesses what is happening in relation to the task, before and after. Only look at the product backlog, design tools, repository, testing environments and analytics when you know how the handovers will work. This means you’re not going to create extra complexity to solve a vague problem. You’ll be able to easily justify your decisions. When looking into app development company in austin, ask what the real business problem is.
Who is the Target Audience?
Whilst it may be tempting to state everyone that could benefit, this rarely helps you make the right decisions. Look at the business sponsor reviewing the development proposal. When does the task become a hassle? What would a truly successful outcome look like? When looking into app development company in austin, consider the day-to-day.
An example of this could be that during discovery, it becomes apparent that the dashboard cannot be delivered without accurate source data. Whilst persona documents can be useful, having an honest reflection of what their week looks like is much more useful. Ask the business sponsor reviewing the development proposal when they do this task, what is causing interruptions and who they ask for help. This can affect what features are required, what resources you’re assuming and the order of delivery. Without knowing the context of the tool, it will be hard to get attention. Be clear on what is essential and what is a nice-to-have. When looking into app development company in austin, ask what the real day-to-day is.
Define Limits
An example of this could be if the agency requests production credentials via an open email thread. Define limits early on. This ensures that you’re protecting your business and the people using the product. Define what the agency will own vs what the client must own. Having these defined in writing means that the development team can confidently say no to anything that goes beyond what has been agreed. When looking into app development company in austin, consider the limits of operation.
Having a design limit means that you’re being practical. This shows what can be achieved by the solution, whilst ensuring that there is a human element and that complex scenarios will be passed onto. By choosing based on cost alone, you could end up with a difficult to maintain application. Define who will approve and how exceptions will be handled. Often teams find that a simple decision table helps to prevent confusion. Define who can resolve the exception. When looking into app development company in austin, ask what the real limits of operation are.
Create a Minimum Viable Product
Create a minimum viable product. This isn’t a mini version of a fully developed platform. This should help you scope a useful product with ownership. Ensure that you’ve got an honest MVP. Try to include a standard scenario and something that could go wrong. An example of this could be that the lowest bidder doesn’t include QA, accessibility and ongoing maintenance. When looking into app development company in austin, consider the first release.
Ensure that the pilot is small enough that you can change things without spending a lot of money. Create a repeatable pilot. Give a small number of people a real task to complete. For example, scoping a useful product with ownership. Give them no guidance and see what they can achieve. Take note of what they succeeded and failed at. If they had to come up with workarounds, then you’ve learned something valuable. When looking into app development company in austin, ask what the real first release is.
Consider the Hidden Costs
Often the cost in the proposal will grab everyone’s attention. However, often the real costs come from training, changes to integrations and fixing exceptions. Before you commit to building, think about vendor costs, product management, testing and maintenance. When looking into app development company in austin, consider the investment.
An example of this could be that the client is looking at some great designs but can’t see how the sign-up process works. Think about what you can define early on. Whilst the first invoice from engineering may look good, someone will be owning the integrations, access to accounts, fixing bugs and changes to the business. Consider vendor costs, product management, testing and maintenance from the start. This isn’t to make the idea seem expensive, it’s to ensure that you know what you’re investing in. Don’t forget that support and training are part of the project. When looking into app development company in austin, ask what the real investment is.
Define Success
An example of this could be that a new API needs to be approved by a 3rd party vendor. This wasn’t included in the timeline. Just because you’ve announced the launch doesn’t mean it’s successful. Ask yourself, are the results improving (business outcomes, defect rates post release) and are people understanding and trusting the work? Define what success looks like with a baseline and reasonable timeframe. When looking into app development company in Austin, consider the evidence of success.
Define what would make your skeptical colleague believe. Something practical like business outcomes, defect rates post release and whether issues are being resolved without exceptional effort. Consider the stats alongside real user feedback. Just because there’s a lot of activity doesn’t mean it’s a success. People may be having to do extra steps that they previously did easily. Get real feedback from users and don’t be too quick to celebrate. When looking into app development company in austin, ask what the real evidence of success is.
Create a Logical Next Step
Once you’ve got a basic version working don’t be tempted to include everything that was put on hold. What has changed in their day-to-day? What has caused confusion? What problem should you focus on? Having a useful next step is better than a big impressive roadmap. An example of this could be that the original project team have left before handing access to deployment. When looking into app development company in Austin, consider the next decision.
Use the evidence to decide what the next improvement should be. A useful handover will give a simple explanation of how things work in practice. Who gets alerted if there’s a failure? Who can change a setting? What logs can be used to investigate? What would make you want to expand the tool? These are just as important as getting the first feature working. This means that you can improve your investment without relying on 1 person. The next stage should be smaller and clearer than the original idea. The best place to start is keep it simple. Write out the problem, who it affects and try 1 useful change. Starting with clarity means you have a solid foundation for your ambitions.
Top comments (0)