Information that should be measured in cultivating the developer community.

Information that should be measured in cultivating the developer community.

I often hear people say that they want to create a developer community for the service of their company. I also often hear people say that while it is good to make a community, they just don’t seem to go well. The problem here is most likely thinking of a community as a qualitative thing, and working it out by feel. Because of that, it becomes hard to tell if more support is needed, or to discover points which require improvement.

This time I will introduce areas of focus for carrying out a developer community.

Number of participants.

If there is only one person registered for 50-person events, you have a big problem. Why does this issue occur?

  • Insufficient notice.
  • Lack of target group.
  • Problems with the content.
  • Location issues.
  • Scheduling issues.
  • Event fare.

These and more can be thought of as answers. In most cases, the cause seems to be problems with the content. Rather than considering what you want to convey, you should focus on what content the audience wants to hear. If the content is too specialized and catered towards a narrow field, there is the chance your target audience will be insufficient from the outset.

If your event charges money for entry the amount of participation registrations will drop dramatically. If you have confidence in the content, there shouldn’t be a problem even if you charge. In this case, the participation rate of the next event will improve by a large margin.

Participation rate.

It is also a problem if 50 people register but only 20 show up. Many people will say that 70% of the developer community attending is a satisfactory result, but I personally do not think that way. The minimum line should be 85% at the least, (25 participants per 30 registrations.) The causes of this problem are outlined below.

  • No reminders are sent.
  • People who register provisionally.
  • Problems with the weather.
  • Free events.

People register provisionally to get in first. Because of that, they register provisionally regardless of whether or not they will actually attend. They only think over whether or not they will attend afterwards, then will cancel their attendance or just not show up. In this case, reception needs to be conducted properly, and repeated no showers should be denied participation.

Participation rates tend to be poor for free events. It seems that people think that because these events are free they can register casually and therefore that its okay if they don’t go.

Repeat rate.

Take a look at the rate of participants who have attended before and those who are new. If your participants are only repeaters or only new, you have a problem. The ratio of existing to new participants should be around 6:4 in general. Please consult The ratio of existing and new participants which cannot be overlooked in community development for further details.

Amount of tweets.

Most developers have twitter accounts. New people are informed through their output. If the community is lively and energetic, these new people might want to participate in the next event.

The amount of tweets is important, but let’s take a look at the number of people tweeting. If a lot of the participants have an account but aren’t tweeting about the event, the cause could be a problem with the content.

Participation report number.

If the amount of reports of participation from blogs, Qiita, etc., increases the presence of the community will broaden. You may as well add a participation box on a blog, but personally I don’t get the impression that many people register through these blog boxes. Rather, it seems to be more effective to ask people to write their impressions on their blogs either during the event or afterwards.

Frequency of holding events.

The more participants you have, the more intense it is, and the more overflowing with content your event is, the more the frequency of event holding increases. Whether or not they should be held once a month or once every three months probably depends on the community. The important thing is to conduct them regularly. The frequency with which events are held is determined by the number of the target audience. Please take care not to run out of content as result of forcing yourself to repeat these events too often.

Number of social gathering and after party participants.

If the event is felt to be enjoyable, many will remain for the social gathering afterwards. Furthermore, those who stay for the after party will be even more eager and there is a chance you can invite them to become management members. People will stay for the social gathering for the content, and there is a high chance they will remain for the after party if the participants and managing members are good. Community isn’t just about the content, the connections between people is important. These connections will of course appear at the social gathering, but will be even stronger at the after party.


Information like that above can be measured quantitatively. And remember to record qualitative information such as the atmosphere of the event. By recording information like this, you can quickly grasp that the participation rate is decreasing and the rate of event holding is falling. Attempting to support something after it has already entered a downward trend is even more difficult than starting from scratch, so dealing with it as soon as possible is a necessity.

MOONGIFT supports community cultivation.

At MOONGIFT, we support the cultivation of developer communities. As the community manager of your company, we nurture developer communities. We aim for communities to eventually propel themselves and run on their own. For those who want to start their own community, or for those having problems with their current community please contact us.



You will receive news and updates about DevRel via email.