1. Initial specifications.
As a client, Paul would work closely with you to establish firstly what you want the site to do - a dream board! Here you write down everything you can think of into a shared document that you would like the ultimate system to achieve. The system specification that solves all your headaches around slow processes that you know can be automated, freeing you up to be able to work more ON the business rather than IN the business.
2. Phase Mapping and final specifications.
The processes are then mapped into systems thinking for the developers to estimate how long it's going to take.
Before a quote is given, the requirements are checked with you first and at the same time we break in down into phases - the core build and then phases that will act as milestones and leaving the more outlandish thing for later once you can see a return on your investment and make a business decision if things are actually worth it or not.
Like that button that instantly pays everyone at the end of the month with 100% accuracy whilst making you a cup of tea! It's possible, but might not be worth the hassle. Worth doing a cost/benefit analysis though as you never know! It might be really good tea :)
Depending on the size of your business or organisation, Paul may meet with the employees in order to draw up an accurate specification of all the needs of the project.
3. Project specification is quoted.
A price is given to you for the project along with expected timelines. We keep these very competitive and the price at final quotation is what we expect. We already discount any wiggle room as we like to be accurate with our pricing. We only create the best systems and you can't put a price on a system that does exactly what you set out for it to do.
4. Colour, design and user experience.
After you accept the proposal, you will liaise with Paul and start work on the look and feel of the system. You'll create a mood board of sorts to use as inspiration for the design. Paul will begin designing the front end of the site in a format that you can go back and forth easily with in order to get it exactly as you want it.
No more surprises on launch day where you get a design revealed only to be horrified as what you described over the phone was NOT THAT! (Yes we've seen that happen before!).
Things like button placement and wording will all be carefully considered at this stage to create a seamless experience for the end user - very important for getting the employees to adopt the system.
We all have smart phones and they are all designed to deliver amazing user experiences so it has to be good if not better than what they are already used to.
Steps 4 and 5 run alongside each other. Whilst you're getting excited about the progress of what the site is going to look like, Shuan and the development team will be working on putting the parts together behind the scenes.
6. Show the employees the prototype
It's very useful at this stage to show the employees the designs of the software - a working prototype. This gives them the opportunity to say if something is off the mark or has been missed out entirely.
Generally new ideas come out at this stage as the working prototype sparks people's creativity. This is the part where you pray that any ideas aren’t expensive and fundamental to the core that somehow got missed off in the beginning! Yeah we've seen that before as well!
This is why we like to do the design process closely with our clients. Some web companies don't like to do this, they want the client to stay away from the design process and leave them to it but we see there is a trick being missed there.
After the feedback sessions, we then incorporate any ideas or suggestions that will improve the system.
7. Phase 1 sign off
When phase 1 build is complete, it will be built into the design Paul will have helped you create so it will feel familiar, however, pressing the functioning buttons on your ‘baby’ for the first time is quite exciting!
8. Launch and feedback
This is when you show the functioning software to the employees for the first time. Paying attention to how they use it and if they did anything unexpected - you just never know how the user is going to use the tool until you watch them.
We then tweak anything that needs tweaking.
9. Rinse and Repeat
Steps 5, 6 and 7 then repeat until the system is fully built and you’re toying with the idea of your super button ;)