HacknPlan focuses on project management for game development teams. Its Game Design Model adds an editor that allows teams to create structured documentation and connect design elements with tasks and production workflows.

Strudo focuses specifically on documentation for game development. Instead of adding documentation as a feature within a project management tool, Strudo is built around it.

The difference is simple: HacknPlan focuses on project management, while Strudo specializes in the documentation that defines a game.

Summary

  • HacknPlan is a task management and production tracking tool for game development teams.

  • Its Game Design Model allows teams to create structured documentation within the project.

  • Strudo specializes in game development documentation.

  • Strudo provides dedicated document types for different areas, including GDD, TDD, LDD, NDD, and ADD.

  • Strudo includes specialized blocks for representing information commonly used in game development.

  • Documentation can be filtered by departments and organized according to its priority.

  • Strudo's REST API provides access to structured documentation from external tools, scripts, game engines, and other systems.

What is HacknPlan?

HacknPlan is a project management tool designed for game development teams. Its main purpose is to organize team work through tasks, boards, milestones, sprints, dependencies, and other production tracking tools.

In addition to these features, HacknPlan includes the Game Design Model, which allows teams to structure elements related to game design and connect them to project work.

This makes it possible to keep certain design elements close to the tasks that use them, without requiring a separate tool exclusively for that information.

For teams primarily looking to manage production work, this combination can be useful.

But there is an important distinction when documentation itself is the main concern.

What is Strudo?

Strudo is a tool built specifically for game development documentation.

Game documentation is more than a collection of text pages. Depending on the department and type of information, it can contain stats, formulas, controls, dialogue, decision trees, state machines, maps, diagrams, visual references, and many other elements.

Strudo is built around this idea. Instead of relying on a single general-purpose editor for every type of information, it organizes documentation through different document types and specialized blocks.

HacknPlan vs Strudo: Two Different Approaches

The main difference is not whether both tools can contain text, images, or design information. Both can.

The difference is what problem each tool is designed to solve.

HacknPlan starts with project management. Design documentation is one of the tools available within that environment.

Strudo starts with documentation. The structure of the document, the information it contains, and the way different departments can use it are central parts of the product.

This makes the comparison particularly relevant for teams that already have a project management system and are looking for a dedicated tool for documenting their game.

Specialized Documentation for Different Areas

One of Strudo's most important differences is that documentation does not have to be organized as a single generic document.

Strudo supports different documentation types:

  • GDD, Game Design Document

  • TDD, Technical Design Document

  • LDD, Level Design Document

  • NDD, Narrative Design Document

  • ADD, Art Design Document

  • DOC, General Documentation

Each can be used for a different purpose within the project.

This makes it possible to separate, for example, game rules and systems from technical documentation, level design, narrative, or art specifications.

A project management tool can store information about any of these areas. The difference is that Strudo is specifically designed to structure this documentation.

24 Specialized Blocks for Game Development Documentation

Strudo includes specialized blocks for representing different types of information commonly used during development.

These include:

  • Stats, for statistics and attributes.

  • Formula, for mathematical formulas using KaTeX.

  • Enum, for enumerations and defined values.

  • Controls, for documenting controls and inputs.

  • Dialogue, for dialogue structures.

  • Decision Tree, for decision trees.

  • State Machine, for state machines.

  • Character, for structured character information.

  • Annotated Map, for maps with contextual information.

  • Diagram, for representing structures and relationships.

  • Media, for images and videos.

  • Mermaid, for diagrams generated from code.

And other specialized blocks designed for different documentation needs.

The difference from a general-purpose editor is not simply being able to write the same information. These blocks allow certain types of data to be represented in a structured and reusable way.

Documentation Organized by Department

Game documentation is often used by people with different needs.

A designer may need to consult systems and rules. A programmer may need technical information. An artist may need visual references and specifications. A level designer may primarily work with maps, layouts, and level elements.

Strudo allows documentation to be filtered by departments, making it possible to show the information relevant to each area of the team.

This means the entire project documentation does not always have to be presented as one large collection of information.

Development Priorities

Not every piece of documentation necessarily represents functionality that needs to exist in the first version of the game.

Strudo allows elements to be classified according to different priorities:

  • Essential

  • Optional

  • Future

  • DLC

This makes it possible to distinguish between what is required for release, what can be added later, and what belongs to potential future expansions or versions.

Documentation can therefore reflect not only how the game works, but also which parts of that design are actually within the current scope.

From Documentation to Game Data

Another important difference with Strudo is that structured documentation does not have to end as a page that is only read by a person.

Strudo provides a REST API that allows structured documentation to be accessed as JSON data.

This opens up different possibilities for teams that want to use that information outside Strudo:

  • Internal tools.

  • Scripts.

  • Custom software.

  • Integrations with other applications.

  • AI workflows.

  • Development tools.

  • Game engines such as Unity, Unreal Engine, or Godot.

For example, an external application can query information documented in Strudo and use it within its own workflow.

This turns certain documentation elements into data that can be consumed by other systems instead of remaining exclusively inside the editor.

Can Strudo Replace HacknPlan?

That is not the goal.

Strudo is not intended to become another task management tool, nor does it need to replace the tools a team already uses to organize production.

If a team uses HacknPlan to manage tasks, sprints, milestones, and development tracking, it can continue using it for those functions.

Strudo can handle the specialized documentation side.

Each tool can therefore focus on the problem it was built to solve:

HacknPlan for managing the project's work.

Strudo for creating and maintaining game documentation.

Can Strudo Be Used Without HacknPlan?

Yes.

Strudo does not depend on any specific project management system. It can be used alongside different production tools, or as a dedicated documentation system for teams that already have other methods for organizing their tasks.

This makes it possible to separate two needs that are often mixed together: managing what the team needs to do and documenting how the game should work.

HacknPlan vs Strudo: Which One Do You Need?

The answer depends on the problem you are trying to solve.

If you primarily need to manage tasks, organize team work, track production, and manage sprints or milestones, HacknPlan is focused on that problem.

If your production management is already covered and you are looking for a dedicated tool to create and maintain game documentation, Strudo is specifically focused on that need.

And if you need both, you do not necessarily have to choose a single tool. You can use one for project management and another for documentation.