Hi! I'm Deb.

Processes should start with a framework but adapt to fit the team you're working with and the feature you're working on.

MVP should reflect Minimum Valuable Product, not Minimum Viable Product. If the first iteration isn't usable and doesn't add value, then you may not get the chance to iterate.

Sometimes, you have to slow down to speed up. Take a beat to work smarter on the right things.

We don't have to address every use case or edge case right away, but we should think of as many scenarios as possible and acknowledge what we're choosing to ignore.

Document your design as much as possible so engineers and testers have clear instructions, but don't toss a spec over a wall; communicate early and often to reduce confusion later.

Step up and step back: as a design leader, I provide the context to let team members do their best, stepping in only to unblock them. I step back when things are running smoothly and step up to facilitate a decision.

Strong opinions, loosely held. Have a guiding principle, but be open to change when faced with new evidence.

Consistency is important, as long as we avoid foolish consistency. Have a visual language, but remember that one size doesn't always fit all.

Iterating is good, as long as we don't abandon our long-term goal for short-term gains.

It is a poor workman who blames his tools. I'm a fan of pen, paper, sticky notes, and anything else that can communicate ideas, whether it's low or high fidelity.