Community Secrets: How Devs Master Design Using Workflow Friction
Subject: Unblocking Your Game Dev: Using Workflow Friction as a Design Compass
Hey team,
Been seeing a lot of devs, especially solo folks, spinning their wheels on features that just…don’t quite land. Hours poured in, code working perfectly, but the player experience feels off. It’s frustrating, right?
The problem isn’t usually a lack of skill. It’s often a lack of clear design vision and a failure to course-correct early. We get so caught up in doing that we forget to think.
Here’s a counterintuitive approach that’s been working for me: embrace workflow friction.
Workflow Friction? Seriously?
Yeah, I know. Sounds backwards. But hear me out. We’re talking about deliberately adding steps to your process that force you to pause, reflect, and articulate your design decisions. Think of it as built-in QA for your design, not just your code.
One of the best ways to introduce this friction is through visual journaling.
Tracking Progress with Visual Journaling Methods
Visual journaling is more than just keeping a text-based game development log. It’s about actively engaging with your design ideas visually and documenting the evolution of your game. Think of it as a sketchbook meets devlog.
Here’s the basic idea:
Capture the Initial Spark: When a new feature idea hits, don’t immediately jump into coding. Instead, sketch it out. Use rough drawings, diagrams, and mind maps to visualize the core concept. Label everything. What problem does it solve? What player experience are you aiming for? This isn’t about art; it’s about clarifying intent.
Document Iterations: Every time you make a significant change to the feature, create a new entry in your visual journal. Note the date, the changes made, and why you made them. Did player feedback lead to the alteration? Did you realize a technical limitation? Be specific.
Identify Friction Points: Here’s where the magic happens. As you work, pay attention to where you feel resistance. Are you struggling to make a certain animation work? Is a particular UI element consistently clunky? These are design signals! Document these friction points in your journal. Ask yourself: Why is this difficult? Is the underlying design flawed? Is there a simpler, more elegant solution?
Reflect and Revise: Regularly review your visual journal. Look for patterns in the friction points. Are you repeatedly running into the same types of problems? This could indicate a fundamental flaw in your overall design philosophy. Use this information to revise your approach.
For example, say you’re struggling to implement a complex inventory system. Your journal might reveal that the complexity stems from trying to allow players to combine too many items. Simplifying the crafting system could solve both the implementation headache and improve the player experience.
Actionable Tips for Starting Your Visual Journal
- Keep it Low-Tech: Don’t get bogged down in fancy tools. A simple notebook and pen are perfectly fine. Whiteboard photos work great, too. The key is to capture your ideas quickly and easily.
- Be Consistent: Aim to make at least one entry per development session. Even short notes are better than nothing.
- Date Everything: This is crucial for tracking the evolution of your design and understanding the context behind decisions.
- Don’t Be Afraid to Scrap Ideas: Your visual journal is a safe space to experiment and fail. Don’t be afraid to kill features that aren’t working.
- Share (Optional): Consider sharing excerpts from your visual journal in your game development log. This can provide valuable insights for your audience and build a deeper connection.
Common Pitfalls and How to Avoid Them
- Treating it Like a To-Do List: A visual journal is not a task tracker. It’s a tool for reflection and design exploration.
- Being Too Vague: Avoid general statements like “Fixed bug.” Be specific about the problem, the solution, and the reasoning behind it.
- Letting it Become Overwhelming: Keep it concise and focused. Don’t try to document every single detail. Focus on the key design decisions and friction points.
- Not Reviewing It Regularly: The visual journal is only useful if you actually use it. Schedule time each week to review your entries and look for patterns.
From Frustration to Feature: A Real-World Example
I recently worked on a small platformer where I was struggling to nail the feel of the jumping. I spent days tweaking the physics, but it still felt off. After reviewing my visual journal, I realized that I was so focused on the numbers that I had forgotten the original design goal: to create a sense of bouncy, cartoonish movement. I scrapped my realistic physics and started experimenting with more exaggerated animations and sound effects. Suddenly, the jumping felt right. The friction (the frustration with the physics) was a signal that I was heading in the wrong design direction.
Visual journaling is about more than just tracking your progress. It’s about turning frustration into valuable design feedback. It helps you identify points of friction, understand the “why” behind your design decisions, and ultimately, create a more cohesive and engaging game experience.
If you’re finding the process of maintaining a visual journal in a notebook to be helpful, consider exploring more robust game design journaling tools to further refine your process. Check out our game design journaling tool here. It’s designed to streamline this workflow and help you capture, organize, and reflect on your design decisions even more effectively.
Let me know if you have any questions or want to share your own experiences with visual journaling.
Best,
[Your Name]