Comment by reneherse

CONTINUED:

I craft UX and frontend design in the browser using a method that's likely a bit different from what you're used to. Your dev team will receive clean, shippable markup & CSS that's ready to be wired up. (Handing off pretty pictures for others to build is not my style.)

This frontend efficiency is only the final piece of a specialized, high-value process of product creation.

The full process can be reduced to these three keys:

1. Object Oriented UX analysis & mapping

2. Rapid prototyping: Multiple iterations of the design-build-use cycle

3. Designing in-the-browser, culminating in shippable code

It's a three part combination that lands the knock out punch every time.

• The process begins with object and data modeling (OOUX) to untangle complexity and find trouble spots. It's a fantastic way to increase your team's awareness of the true scope of your product and tease out unspoken wisdom trapped in mental or organizational silos.

• Next, we'll agree on a design brief, and the rapid prototyping phase begins. I'll then proceed quickly from sketchbook to code to browser. (I usually skip Figma unless there's a need for establishing brand & identity.)

• The work on your project will proceed iteratively, in the original (not "Agile") sense of the word. We'll iterate through multiple design-build-use cycles of delimited, self-contained user experience (not just a random fragment or slice).

• The feedback & lessons we gain from each iteration will inform our goals for the next cycle. Each iteration is a step forward in "how it works" as well as appearance and code. The final iteration represents an optimal user experience written in code that's ready to ship.

Sound fun? I've been doing this for over ten years and it works.

I'm currently available to work on a fractional basis with technology and SAAS teams. Let's schedule a brief call, see if there's chemistry, and get down to it!

email me:

scott [@] designerwho [DOT] codes

https://designerwho.codes