Story about problems that cannot be solved by adding features
The problems discussed in the previous article
were not due to the shortcomings of specific tools.
- It's not because WordPress is lacking
- It's not because Notion or Excel are bad
There was only one problem.
It was not viewed from the perspective of 'operating' but only from the perspective of 'writing' a blog.
Most blog tools start with the same question
Existing blog tools
generally start from this question.
"What do individuals need to write comfortably?"
So the focus is always on this.
- Convenience of the editor
- Design and themes
- SEO options
- Publishing speed
All of these are important.
But they are not sufficient for agencies.
Agencies need to ask different questions
When operating a blog at an agency,
the real important questions are different.
- Whose responsibility is this blog?
- When and how is this account recovered?
- Where are mistakes prevented?
- Will it be operated in the same way even if people change?
If these questions are not answered,
no matter how good the features are,
it becomes a burden to operate.
blog.haus started from these questions
blog.haus
did not start from the question,
"How should we make the editor?"
"When agencies operate multiple blogs,
where is the first point of collapse?"
The answer was clear.
- The moment accounts are mixed
- The moment permissions become unclear
- The moment responsibility is assigned to a person
So the design criteria changed.
Structure-centered, not individual-centered
At blog.haus,
the stability of the structure takes precedence over individual convenience.
- Blogs are separated from the beginning
- Permissions are divided by role
- Who did what is tracked
This is not about "using it well"
but an approach of "preventing misuse."
Features are the result, not the purpose
Multi-blogs, team collaboration, permission management.
These are not features of blog.haus.
They are results that naturally follow from operational standards.
That's why blog.haus
does not boast about features.
Instead, it anticipates these situations.
- Does the explanation decrease when a new person comes in?
- Is there no confusion when the practitioner changes?
- Is responsibility clear when problems arise?
If you can answer "yes" to these questions,
then the structure is well-made.
It's not a tool for better writing
blog.haus
is not a tool to help write blogs better.
It is closer to a tool that eliminates worries about blog operation.
- You don't have to worry about where to post
- You're not anxious no matter who writes
- Management does not rely on individual capabilities
This difference grows over time.
Structure quietly makes a difference
Good structure doesn't stand out.
But bad structure will definitely cause problems.
What blog.haus aims for is
not admiration like "Wow, this is convenient," but,
"Now I don't have to worry about this."
In the next article,
I will discuss how this structure actually reduces risks,
and why the mindset of blog operation
inevitably leads to "at some point, once."
Next Episode Preview
〈Why do agency blog operation mindsets always occur in the same way〉