In July 2011, the digital landscape felt both crowded and raw, and my creative output reflected that messy middle ground. This collection of July 2011 crap I made captures half-formed ideas, rushed experiments, and small victories that shaped my approach to content and design.
Rather than polish everything into a highlight reel, I kept the rough notes, the abandoned drafts, and the awkward prototypes, because they reveal how my process actually works under tight deadlines and shifting priorities.
July 2011 Project Portfolio Snapshot
| Project | Type | Tools Used | Completion Status | Key Lesson |
|---|---|---|---|---|
| Responsive Wireframe Set | Design | HTML, CSS, Photoshop | Partial | Layout assumptions break fast at small sizes |
| Data Viz Experiment: Global Temperatures | Visualization | Processing, Illustrator | Complete | Simplified scales communicate more clearly |
| Microcopy for App Onboarding | Content | Pen, paper, whiteboard | Complete | Short phrases reduce cognitive load |
| Scripted Demo Video Storyboard | Video | Paper, Keynote | Partial | Dialogue must sound human, not marketing |
Design Experiments and Constraints
Rapid Layout Testing
I built a series of quick layout experiments in July 2011 to challenge my habit of over-polishing early drafts. By limiting each layout to ninety minutes, I forced decisions and accepted that imperfection can be informative.
Grid Breakage and Learning
Several grids fell apart when viewed on real devices, exposing gaps in my understanding of fluid columns. Those broken layouts became the most valuable artifacts, because they highlighted exactly where my assumptions needed to change.
Content Writing and Microcopy Challenges
Voice Under Time Pressure
Writing tight microcopy without losing a distinct voice proved difficult, yet it taught me how to balance clarity, personality, and space constraints in headlines, labels, and error messages.
Labeling for Accessibility
Even small pieces of content needed thoughtful labeling so that screen reader users could complete core tasks. Those choices pushed me to think beyond visual hierarchy alone.
Technical Tools and Workflow Choices
Tool Limitations as Creative Pressure
Using Processing for a data visualization and basic HTML for rapid UI shells exposed tool trade-offs. Instead of chasing the perfect stack, I focused on finishing meaningful artifacts quickly and iterating later.
Version Control for Early Drafts
Simple file naming and lightweight version tracking kept me from losing earlier ideas. It also helped me compare iterations objectively and explain my choices to collaborators.
Moving Forward with Imperfect Work
Treating these early artifacts as learning milestones rather than finished work reshaped how I approach future projects.
- Document assumptions alongside each prototype so decisions are traceable
- Set short, time-boxed experiments to force decisive action
- Capture small wins and lessons in a central log for later reference
- Share rough drafts early to invite constructive feedback
- Separate exploration from polish to keep creative momentum
FAQ
Reader questions
How do I decide what to keep and what to discard from these early drafts?
Keep artifacts that reveal a change in your assumptions or workflow, and discard ones that only repeat the same comfortable patterns without new insight.
What is the most common mistake you see in rushed visualizations?
Overloading a single chart with too many series and relying on color alone to encode meaning, which makes the visualization hard to read at a glance.
Can microcopy learned in July 2011 still apply to modern product interfaces?
Yes, principles like brevity, plain language, and consistent tone remain essential, even as interaction patterns and platforms evolve.
What is the most valuable lesson you took away from broken prototypes?
That exposed failure points are a gift, because they highlight risks before they reach users and give you a clear rationale for redesign decisions.