• Thomas Michael SemmlerThomas Michael Semmler, over 1 year ago

    Let's say I sent a design to devs for them to start coding it. After a while I have to change something in the design, based off some feedback or after metrics come in.

    I develop everything I design myself, so that specific thing is not a problem, but in our team we do have a clear rule about design phases. We have four of them and many people take part in them, including stakeholders and developers:

    • research
    • planning
    • visual design
    • implementation

    We don't allow ourselves to go into any phase, unless the first one is done. So if you have to change something in the design, based off some feedback or after metrics come in, then your research phase was not done yet.

    • In research, you gather metrics, ideas, loosely defined wishes and goals for what you are supposed to design.
    • Then in planning, you allocate, gather plan all the resources you'll need, from design to implementation. This is also the right phase for low fidelity design work, like wireframes and prototypes and to gather last decisions that have big impact on the visual design phase.
    • Following visual design, where you actually sit in front of the program of your choice to create mockups that show how the final product will look and feel.
    • and of course implementation itself. Where you... implement.

    If you honour the boundaries between design phases, then there are no questions unanswered when implementation happens.

    Your Situation shouldn't occur, because if you don't start designing until you have all needed information, then there won't be any implementation that needs to be cancelled. Vice versa, when implementation has started, don't design anymore. It is done. Do not start development unless design is completely done.

    The only thing that won't make this process painful are barriers and respecting them. A clearly defined process can be a guideline for all and prevents conflicts and frustration from arising.

    0 points
    • Jan Vu NamJan Vu Nam, over 1 year ago

      Thanks for your lengthy comment Thomas! I appreciate the effort!

      In the ideal world - yes, this should be the practice. Sadly, in the world or startup hustle, things can and do change very fast.

      Especially when your team is working on one particular product, you will never be really "done". You can never see all the cards in the deck at the start, and some things you simply don't learn until some real users get their hands on your product.

      It's a classic iterative design mantra - Plan - Prototype - Feedback - Implementation - Evaluation - Plan …

      It's simply necessary to keep growing your product, and there will be no perfect research or a masterplan in the beginning that will guarantee you a unicorn in a first go - but rather years of carefully listening to your users and delivering.

      That sometimes means changing the design too… in smaller or bigger ways.

      0 points