We work “With” our Clients and not just “For” our Clients – Think201 Manifesto
Every business smaller or bigger has a manifesto of values it strongly believes in delivering to its customers. After having grown about double the team size and revenue from last fiscal year, we recently decided to declare our own company manifesto too in order to broadcast the philosophical ideologies that have helped us in growing sustainably without any external funding whatsoever.
Our manifesto has also helped in propagating the synchronous attitude among the team members to talk in similar lines as that of our core ideologies upon which Think201 was founded.
We, out of our passion to build tech products, are able to serve our clients. The bunch of Thinkers at our office like to fundamentally understand every user journey of the platform for any business before starting the development work.
We brainstorm with our clients to understand the target users demography, value additions to the users from the clients’ product/service and USPs of the clients’ businesses so we can make rational decisions in the creation of UI/UX mockups and in the decision of a relevant tech stack for the business needs. These brainstorming sessions with our clients provide us insights to choose the right color schemes in conveying the similar emotion as that of the brand, strategically order the messaging on the website or landing page for a smooth storytelling of the brand to communicate with their customers and deciding on the relevant Call-to-Actions that need to be emphasised for promoting user engagement and leads generation.
As Einstein said: “If I were given an hour in which to do a problem upon which my life depended, I would spend 40 minutes studying it, 15 minutes reviewing it and 5 minutes solving it.”
We follow the similar philosophical analogy by dividing our product development cycle into 3 steps:
1. Feature Requirement Specifications (FRS) — From the initial brainstorming with our client, we document a Feature Requirement Specifications wherein all the user personas, respective user workflows for all the core features of the client’s business are listed.
2. Interactive UI/UX Design Mockups — Upon the approval from the client after a couple of feedback tweaks, our Design team initiates working on theming the whole product around the target user demography and the core values (and industry-specific standard) of the product. It’s this stage where both the client and the Project Manager can realize few workflows weren’t completely thought through.
The above two steps, therefore, become open for reviews and verification of the complete product user journeys. New screens can be introduced as part of improving the UX.
It wouldn’t be wrong to say that the above two steps analogously comprise 55 minutes of an hour.
3. Development — When all the flows and mockups are finally frozen, we get to the tech development of the platform. With all the above two steps taken seriously, our clients are pretty sure of what they should be expecting at the end of the product development.
Post the development, the Quality Assurance Engineers work towards making sure the product is functioning as expected before deployed to production.
Our Feature Requirement Specifications document and the design mockups are the triggers for both the parties to completely think through every user flow in the platform and confirm on the same. We suggest these processes not to be taken lightly since it prevents any possible future confusion on any feature.
We don’t shy away from asking our clients if any of the processes or flows are not completely thought through. We work best when we are allowed to exercise our creative freedom to bring out the best results.
We believe that we work with our clients in realising their dreams instead of working just for our clients. Therefore, we expect that we work as a team and can frankly “Agree to Disagree” in a discussion.
Feel free to contact us on email@example.com if you feel we would be a great fit to work together in building awesome products.