When to Use Kanban Instead of To-Do Lists: Devlogs

Posted by Gemma Ellison

August 4, 2025

Ditch the To-Do List: Kanban for Killer Devlogs

Indie game development is a marathon, not a sprint. And your devlog? It’s the chronicle of that journey. But are you still managing it with a simple to-do list? If so, it might be time for an upgrade. As your project grows, so does the complexity of your devlog strategy. That simple list just won’t cut it anymore.

The transition from hobbyist to serious indie often means adopting more structured workflows. This is especially true for your devlog. A well-maintained devlog is more than just showing off progress. It’s about building community, getting feedback, and documenting your creative process for future reference.

So, how do you take your devlog from “random updates” to "strategic content"? Let’s talk Kanban.

Why To-Do Lists Fail Devlogs

To-do lists are great for simple tasks. But devlogs require nuance. They involve planning, drafting, review, and publication. A linear list struggles to capture this multi-stage process.

Here are common pitfalls when relying solely on to-do lists for devlogs:

Inconsistent Updates: Life gets busy. That “write devlog” item gets pushed down the list, and weeks turn into months.
Scope Creep: You start writing and suddenly you’re detailing every tiny feature. A focused update turns into a rambling mess.
Lack of Prioritization: Are you focusing on what your audience wants to see, or just what you feel like writing about?
Missed Milestones: Did you forget to showcase that major feature release in your devlog? A list doesn’t remind you of these critical moments.

Level Up: Kanban for Devlog Management

Kanban boards offer a visual, flexible system for managing your devlog workflow. Instead of a flat list, you have columns representing different stages of the writing process.

Here’s a sample Kanban setup:

Ideas: Brainstorming topics, feature showcases, community questions to address.
Drafting: Writing the actual devlog post, gathering screenshots, creating GIFs.
Review: Proofreading, getting feedback from peers, ensuring consistency.
Published: The devlog is live! Time to share it and engage with your audience.

This structure allows you to visualize your devlog pipeline and identify bottlenecks. Are you stuck in the “Drafting” phase? Maybe you need to allocate more time or break down the task into smaller, more manageable chunks.

Prioritizing Your Devlog Content

Kanban isn’t just about moving tasks across columns. It’s about prioritizing what matters most. Here are some factors to consider when prioritizing devlog tasks:

Audience Engagement: What topics have resonated with your audience in the past? Double down on those.
Development Milestones: Are you nearing a major release? Focus your devlog on showcasing those features.
Community Feedback: Are players asking about specific aspects of your game? Address those questions in your next update.

Consider assigning priorities (e.g., “High,” “Medium,” “Low”) to your Kanban cards. This helps you focus on the most impactful content first.

Tracking Your Daily Progress

Kanban provides a high-level overview of your devlog workflow. But what about the day-to-day grind? How do you capture those fleeting ideas and insights that emerge during development?

Supplement your Kanban with daily journaling. Jot down your progress, challenges, and breakthroughs. These notes can be a goldmine of content for future devlog posts. They also help you reflect on your process and identify areas for improvement.

The best way to keep a consistent game dev journal is to use these handy devlog journal templates[/journal] to capture daily progress and insights!

Common Devlog Mistakes (and How to Avoid Them)

Not Having a Consistent Schedule: Aim for a regular cadence, even if it’s just once a month. Consistency builds anticipation and keeps your audience engaged.
Being Too Technical: Remember, you’re not just talking to other developers. Explain concepts in a way that everyone can understand.
Ignoring Feedback: Your audience is your best source of information. Pay attention to comments and suggestions.
Treating it as a chore, rather than a celebration of the work you’re doing: Get excited about it.

Case Study: From Chaos to Clarity

Imagine an indie developer, let’s call him Alex, working on a sprawling RPG. Initially, Alex used a simple to-do list for their devlog. Updates were sporadic and unfocused.

After switching to Kanban and incorporating daily journaling, Alex saw a dramatic improvement. Devlogs became more consistent, content was more engaging, and Alex felt more connected to their audience.

The power of Kanban lies in its adaptability. Tailor it to your specific needs and workflow. Don’t be afraid to experiment and iterate. Your devlog is a living document, just like your game. Embrace the journey, track your progress, and share your story with the world.