reneherse
...joined 15 years ago, and has 3906 karma
submissions / comments / favourites
Hi! I'm Scott, a "designer who codes". I'm a principal product designer/builder, consultant and founder working remotely in Atlanta, GA, (previously San Francisco and Berkeley, CA).
IF YOU... -have a dev team that needs design support -are frustrated with UX strategists who leave you hanging when it's time for implementation -see pitfalls in the split between design & engineering -want to learn a better way to design, build & test your product -are not afraid to shake things up if it means your team can ship something awesome every time...
...we should talk.
I craft UX and frontend design in the browser using a method that's probably 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. Because handing off pretty pictures for others to build is not my style.
And this frontend efficiency is only one part of a specialized, high-value process of product creation.
When I engage on your project, our collaborative process will begin with object and data modeling (Object Oriented UX) to untangle complexity and find trouble spots. It's a fantastic way to increase your team's awareness of the broader scope of your product and tease out unspoken wisdom trapped in mental or organizational silos. (One of the knock-on benefits: The "bombs" we'll uncover & defuse can save days or weeks of dev rework.)
Next, we'll agree on a design brief. I'll then proceed rapidly from sketchbook to code to browser. (I skip Figma unless there's a need for hi-fi visual assets or establishing brand & identity.)
The work on your project will proceed iteratively, in the original (not "Agile") sense of the word. In our quest to create optimal solutions, we'll go through multiple design-build-use cycles of delimited, self-contained user experience (not just a random fragment or slice).
The feedback and lessons we gain from each iteration of the UX 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.
If the merits of this approach speak to you, reach out at my email below.
I'm currently available to work on a fractional basis with technology and SAAS teams. Let's have a brief call, see if there's chemistry, and get down to it.
email me: scott [@] designerwho [DOT] codes
(P.S. Despite my username, I have no relation to the Rene Herse bicycle company, maker of some of the world's most beautiful, highly integrated and drool-inducing lightweight steel bicycles. Can you tell I'm a fan?)