Planning and Managing Drupal Projects

After the Handoff: The project retrospective

“Unfortunately, this critical step [of reflecting on a project after its completion] is nearly always ignored by professional designers. Assessment implies internal criticism, something many companies prefer to leave up to public relations or external product reviews. The assessment [of the project’s success] must be at a user and project level, rather than a quality assurance level, and benchmarks for success have generally not been developed or acknowledged within corporate America. In many high-pressure design consultancies, to reflect is to waste time. Reflection is not productive and is frequently viewed as a poor use of money and resources.”^[9]

The case study. Some designers swear by them as a valuable marketing tool; others refuse to do them, insisting that there’s just “too much work to do,” or insisting that images of their work will speak for themselves. I’ve even heard designers say that clients don’t like reading case studies. I’ve never personally seen this, but then, I’ve never quite subscribed to the idea of being “too busy to read.”

Let me state one thing emphatically: reflecting on your work—whether you share them as case studies or not—is vitally important to your career as a designer. Whether you’re part of a team, an independent designer, or working in corporate America, the time that you take to think over a project—how it went, what went right, how you can make things better next time—is one of the most important things ...