Our blog

Page 2 of 2

  • Our 4 Questions

    Souvik Das Gupta

    Introducing projects to someone else who will bring your ideas to life can get really painful. We know, we’ve faced it ourselves.

    Most respected web design shops have identified this problem and have attempted to solve it by using questionnaires with 15 to 20 questions as a starting point of introduction. A long questionnaire, almost as good as detailed documentation can be difficult to answer at such a nascent stage. Thoughts at this stage of a project are usually clear at the micro level, but most macro level details get clearer only as one progresses with the execution. Many a times one looks to seek advice rather than knowing it all. Steve Jobs nailed it when he said It isn’t the consumers’ job to know what they want.” We concur. Such questionnaires are a step to simplify things, but we think that it could be made simpler.

    Going by our Keep it Simple, Stupid principle, we have come up with just 4 questions. These are the most basic and natural questions you would encounter whenever you go out to buy anything, be it a table, a shirt or a computer.

    Hi, how can I help you?
    I want to buy a computer.

    For whom?
    My son, he’s 15. And sometimes my wife will use it, though she doesn’t know much about computers.

    What will they use it for?
    Well, simple things, maybe play some games and watch a few movies. And of course, browse the internet.

    A customer should never be expected to specify how fast the processor should be or how much power the device should draw or even whether he needs a mouse (iPads for instance don’t have a mouse, but can still serve his purpose). If they know, that’s good, but we suggest consulting the experts before forming a mindset.

    However, unlike buying things off-the-shelf, customised design and development jobs provide a huge room for flexibility. Hence it is very important to determine the size of the project. I want my website to look like that” or I want the website to have this feature” is a very small portion of the large pie. Micro level product definitions do not take into account the optionals like legacy browser support, responsive design, CMS integration etc. In many cases these variable components drastically affect the size of the project.

    One way of defining size is by investing significant time and money documenting every little detail of your project. Unfortunately, making this list exhaustive is nearly impossible. Additionally, rarely does such a document go unaltered as a project progresses. No surprises that we prefer not taking this route. The other way of estimating size is by knowing the time and budget constraints. Well, everyone has a budget up their sleeves, but very few like to share it. While we understand their concerns for not being looted by a design shop, it is important to appreciate that the same goals may be achieved by drastically differently sized projects.

    The 4 Questions
    1. Your project in 140 characters (or less).
    2. Who are your primary and secondary set of targeted audience?
    3. What are your 3 most important expectations from the users who visit your project?
    4. What are your time and budget constraints?

    If clients share definitive and unambiguous answers to these 4 questions, everything else falls in place. That is why we have put soft constraints (140 chars, 3 expectations etc.) on every question. At this stage, we want only the essential user-centric’ goals of the project. Our designs are user-focused and these goals have our primary attention throughout. We know that only happy users translate into long-term happy clients. Nothing else matters.

  • The Sweet Spot

    Prateek Rungta

    I remember attending a guest lecture during my first year at Monash University. The speaker, who was an engineer (and an alumni), touched on a lot of things pertaining to Engineering Profession’. One thing that stood out in particular was that most engineers she knew were working in fields different from what they had studied as an undergrad. Now I had already come across a lot of people with a disconnect between their profession and their educational training, so this wasn’t exactly a revelation. But while the lecturer’s motive might have been to highlight that engineering was more about problem-solving and real-world solutions than a specialisation in pure science, I realised something else. I could not help but remark the major overlap between people who’s work I admired and people who had switched career paths since college.

    It is a long journey discovering what one is passionate about, good at and what earns them money. And it is the combination of these things — the sweet spot, if you will — that we’re hoping to achieve with Miranj.


    Copyright Bud Caddel

    We’ve started Miranj because we are passionate about design, building things, writing code and above all, experience — enjoying what we do. Backed by our solid understanding of the web, we’re good at simplifying user experience, designing clean interfaces, developing robust applications and of course, keeping our promises. Besides, people are willing to pay to bring their ideas to life.

    As time goes on, we hope to continue growing our sweet spot. We wish to create more value for this world with people who have good taste, enjoy their work and are raring to take on the next challenge.

    The journey of finding ourselves has been long, but we’re just getting started.