I was trying to suggest to a friend’s company, “Why don’t you implement esa?” I was trying to verbalize what esa is good for in order to make a proposal, but when I thought about a world without esa, I realized that even for a single report, the format is so tacit knowledge that a newcomer can’t write even if given only WORD 1240124070982823937
I don’t know what you mean by “think of a world without esa, where the format of even a single report becomes tacit knowledge,” so I don’t think that explanation gets the point across.
- If the various reports are scattered across personal desktops and shared folders, the cost of finding them is extremely high.
- Having the report in an easily viewable location will formalize the report and help the newcomer get up and running faster.
- Like this? Is it because I used tacit knowledge in a negative sense, as in "only some of the existing employees know about it"?
- It appears to speak to the benefits of "information being shared".
- It's bad enough that it's "dissipating" and doesn't speak to any esa-specific benefits.
- For example, if someone I meet for the first time says, "I've been to Cybozu before," I search Garoon by their name to discover their report.
- I guess the difference between esa and other CMS is that esa can currently publish articles in WIP.
- The system provides an atmosphere in which it is acceptable to put out something unfinished.
- The rest is edited by the article owner and PR.
- With a wiki, it looks like it belongs to the company, and then the wiki police show up to point out the content and choke it off.
- in other words
- The design design promotes the sharing of written material while still attributing it to the individual."
- Since it's attributed to an individual, unlike a wiki, which is attributed to everyone, others will submit suggestions for revision to the author rather than suddenly rewrite it."
- You mean...?
- Yes, that is the reason for the recommendation.
- That's in depth, though, and I'm sure the reasons for the recommendation on the surface will help prevent dissipation.
- If it is just "sharing what you are writing," it can be applied to Scrapbox, etc., but "the editing rights belong exclusively to the individual at the stage of writing" is certainly an interesting point.
- Conversely, a system that notifies others when a draft is published is undesirable because it reinforces the practice of "not publishing a draft and then submitting it after it has been completed.
- Yes, I think it is well done because the notification flies when the finished draft is ready.
- And then there's Markdown, so it's a hierarchical way of thinking about things,
- Is it a cost savings in running the workflow in github afterwards?
- I would recommend such things to previous companies.
This page is auto-translated from /nishio/esaの良いところ using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I’m very happy to spread my thought to non-Japanese readers.
I was trying to suggest to a friend’s company, “Why don’t you implement esa?” I was trying to verbalize what esa is good for in order to make a proposal, but when I thought about a world without esa, I realized that even for a single report, the format is so tacit knowledge that a newcomer can’t write even if given only WORD 1240124070982823937
I don’t know what you mean by “think of a world without esa, where the format of even a single report becomes tacit knowledge,” so I don’t think that explanation gets the point across.