How is design structured in your organization?

over 6 years ago from Cody Iddings, Experience Designer for the moving world

  • Dirk HCM van BoxtelDirk HCM van Boxtel, over 6 years ago

    Hahahaha structure!

    Nah, all jokes aside; many organisations I've worked with/for had setups for infrastructure. Unfortunately, my current one is so fast-pased that I find myself wearing ALL the hats, some of the time.

    • Generally a brief consists of "we need a website for X", or "we need to build product Y", or "we want to market service Z".
    • My next move is to find out more about the product, catalogue it.
    • Chase all stakeholders to help me write a description of the product (features, pricing, target audience, etc)
    • Solo whiteboard session for brainstorming the ideal solution
    • Talk to dev/CEO to identify what resources we have
    • See how close we can get to that ideal solution with the provided resources and available infrastructure
    • Hand-drawn/Photoshop/HMTL mockups, or straight-up implementation

    This includes a lot of copy-writing and coming up with slogans and any/all research I can do into the target audience.

    It's rough, but it's a real-world example that I want to share because a lot of organisations (even medium sized businesses) still work like this.

    Not ideal, but we achieve a fair bit!

    9 points
    • Aaron Wears Many HatsAaron Wears Many Hats, over 6 years ago

      I'm in the same boat as you... I get lumped with everything from storyboarding, to wireframing for apps, to product design, to UX/UI, to front end development, to devOps, to social media management, to... you get the picture.

      SME life I guess.

      3 points