Victus Spiritus


Dynamic Design Patterns: A Hybrid Solution

22 Jan 2010

If it ain't broke, leave it alone? Break it now anyway? Or break something new?

Two design patterns compete for adoption: Do No Harm, and Continual Beta. This post suggests a strategy for keeping the best features of both methodologies.

Do No Harm

The Do No Harm philosophy may be adopted after other early design methods. Do No Harm may begin from a bear bones form of minimalism, with only a single desirable feature implemented. Or Do No Harm may follow an unstable alpha/beta period. Once a design finds market traction, the breaks are put on and changes are made only when absolutely necessary. Afterall, how much change can users reasonably tolerate? A great example of Do No Harm is the web dating company Plenty Of Fish. Architected by a single designer (its founder Markus Frind) the tool has caught a massive market. Markus tweaked the interface only when absolutely necessary.

Riding the Edge Means Continuous Beta

Never settle. Never sleep. The mantra of Continuous Beta is to be ever changing. The market environment is dynamic so why should designs be any less malleable? Continuous Beta seeks iterative change ahead of the market when possible. The goal of design is to trail blaze, leaving other products to copy tactics, while driving market forces trample over static thinking.

The risks of continuous change include copycats and stability. A copycat may do a better job of matching a product to user needs now. Without great care and resources stability may suffer, due to constant flux of the design. Product #fail alienates paying customers (and free users).

Example of Continuous Beta success stories include

The space of web programming is ripe for heavily iterative processes. Streamlined external interfaces and new functional combinations drive software evolution. Early prototypes are hacked together feverishly, then torn down and remade. Each release may frustrate some users while satisfying others. Devs that seek wide audience adoption have to make this exchange to increase their user base.

Dynamic Design Patterns: A Hybrid Solution

A hybrid design solution focuses on the best aspects of Do No Harm and Continuous Beta. The design favors change or stability as necessary driven by the current and expected market.

The greatest feature of Do No Harm is that it is a working solution for at least one community now. The user interface and experience may be just right.

Continuous Beta recognizes that what works today will not work tomorrow. User needs change and heavier network connectivity offers new opportunities.

The Hybrid: Begin with the mantra of Continuous Beta at project inception. After each major version release, determine if the product is better off transitioning to a maintenance phase, or to continue to be replaced by new versions with potentially large UI/UX changes. Even a pure minimalist single feature design falls into this pattern. The Continuous Beta period ends when the feature is selected, and no additional features are added without major market pressure.

If the current market is saturated and research dictates little change in user desired features, you have clear signals to transition a product into a maintenance phase. Optimize the hell out of your current model and squeeze every ounce of performance out of it.

The project may fluxuate from dynamic to stable, but a large reverse of this trend is a signal for a complete redesign.

Great Inspiration from: