Comedy is easy, proposals are hard. Even the toughest creative pros cringe when it’s time to put one together. Yet doing so is essential if you want to keep your doors open. A compelling proposal requires more than a jumble of clichés and a nervous estimate of costs. It needs structure, organization, and joie de vivre. Fortunately, you can provide that structure, no matter how complicated the final proposal needs to be. Learn the key questions every client needs answered, and how to use them as the basis of a proposal that convinces your client you’re the right team for the job.
If you work in any kind of service industry you’ve undoubtedly come across the Request For Proposal, or “RFP.” The RFP process has become a standard by which organizations solicit competitive bids. It attempts to level the playing field and minimize bias by holding everyone to the same requirements, no special treatment, no rule bending. In return, the organization issuing the RFP is able to select a vendor by comparing apples to apples. Alas, in practice, RFPs are the least creative way to hire creative people. The rigidity of the process, and the lack of meaningful dialogue makes this little more than a game of roulette. How can we successfully navigate the heartburn-inducing RFP process? And what can we as an industry do to turn RFPs into the exception rather than the default means of hiring an agency?
Every language app in your pocket inherited a teaching method built for Latin. Understanding why that happened is a more useful design lesson than anything the apps themselves can teach you.
Designers are good people. Some designs exclude people anyway. Alan Dalton offers a practical fix: accessibility personas that help you recognize problems while you're designing, not after. Homework included.
Computing was born in a Viennese café. Between 1928 and 1934, while Hitler plotted and Europe crumbled, a motley crew of mathematicians, philosophers, architects, and economists gathered weekly to puzzle out the limits of reason—and invented Computer Science in the process. What made their collaboration possible wasn't just brilliance (though they had plenty). It was amiability: the careful design of a social space where difficult people could disagree without destroying each other. Longtime Web Dev Notes contributing author Mark Bernstein mines this forgotten history for lessons that might just save today's embattled web from its worst impulses. Spoiler: it involves better coffee service and the looming threat of public humiliation.
Design systems aren't component libraries—they’re living languages. Rigid adherence to visual rules creates brittle systems that break under contextual pressure. Fluent systems bend without breaking.
Having both a Design Manager and a Lead Designer on the same team is beautiful, but can be messy. To make it work without creating confusion, overlap, or “too many cooks,” check Michel Ferreira’s Holistic Framework for Shared Design Leadership.
Building towards bedrock means sacrificing some short-term growth potential in favour of long-term stability. But the payoff is worth it: products built with a focus on bedrock will outlast and outperform their competitors, and deliver sustained value to users over time. Liam Nugent shows us how.
At a time when budgets for user experience research seem to have reached an all-time low, how do we get stakeholders and executives alike invested in this crucial discipline? Gerry Duffy walks us through how the research we conduct is much like telling a compelling story, complete with a three-act narrative structure, character development, and conflict resolution—with a happy ending for researchers and stakeholders alike.
Web Dev Notes founder and web design OG Zeldman ponders the moments of inspiration, the hours of plodding, and the ultimate mystery at the heart of a creative career.
