> ## Documentation Index
> Fetch the complete documentation index at: https://lib.findy.co.jp/llms.txt
> Use this file to discover all available pages before exploring further.

# DevRel principles: how Findy decides which events to run

> The principles behind Findy's DevRel decisions, and guidelines for applying them when planning events.

## Overview

This page describes the principles Findy's DevRel team uses when deciding
whether to run an event and how to shape it.

The page first states each principle with its reason, then gives
guidelines for applying the principles when planning events.

## Principles

### Judge by whether all three parties benefit

An event is worth running when it is good for the organizer, the speakers,
and the participants at the same time. This is the most central criterion,
and the others below can be read as refinements of it.

The reason is that an event depends on all three continuing to take part.
Participants who learn nothing stop coming, speakers who get no useful
opportunity to share their work stop accepting invitations, and an
organizer whose events do not fit its values cannot keep funding them.
An event that sacrifices any one of the three may succeed once but cannot
be repeated.

In practice, check three questions before deciding:

| Party | Question to ask |
| - | - |
| Participants | Is there a specific person who would learn something from this event? |
| Speakers | Does this event match what the speaker wants to share, and is it a useful opportunity for them? |
| Organizer | Does the theme fit the organization's services and values? |

### Face engineers rather than chase attention

When there is a choice between attracting attention and serving the
target engineers, choose the engineers. Thinking about attendance alone
tends to pull titles and themes toward sensational or provocative
expressions.

The clearest case is fear. Titles that warn readers they will fall behind
or that a technology is finished may attract attention once, but that
attention does not last. Aspiration is a positive asset that people return
to; fear is not. DevRel builds on engineers' attachment to technology and
community, so communication that relies on anxiety damages the trust it
depends on.

### Do not decide for the numbers alone

Business numbers such as attendance matter, and DevRel is run as a
business, not as volunteer work. Even so, a decision made only to raise
those numbers is not a good decision.

The reason is that numbers can be obtained in ways that serve none of the
three parties. Asking a well-known person to repeat a familiar talk will
usually draw a crowd, but it adds little to what participants already had
access to. When an event can be explained as good for all three parties
over the long term, it is worth trying even if its short-term numbers are
uncertain.

### Step up to the plate, and drop plans readily

The result of an event cannot be known until it is held. An event expected
to do well can struggle, and the reverse happens as often. If the
organizer can review the result as their own responsibility and carry the
lessons into the next event, trying is better than waiting.

The same principle applies before the event. Dropping a plan when research
or interviews do not support it is a normal outcome, not a failure.
Forcing a weak plan through rarely works, while a dropped plan often
becomes material for a later one.

### Keep ownership of the plan

The person who plans an event keeps the decisions. Consulting colleagues,
interviewing engineers, and receiving introductions to speakers are all
part of planning, but none of them moves the decision to someone else.

Two reasons support this. First, a plan without an owner drifts with each
person's opinion and loses its target and goal. Second, introductions rely
on trust built by the people who make them. Researching carefully and
following through is how the planner keeps that trust intact.

### Where the principles appear in the Online Events page

Several decisions in the [Online Events](https://lib.findy.co.jp/devrel/online-event.md) page come
from these principles.

| Decision in the Online Events page | Principle it comes from |
| - | - |
| Settle the talk theme by asking the speaker rather than prescribing it | Judge by whether all three parties benefit |
| Avoid titles that stir anxiety or rank technologies | Face engineers rather than chase attention |
| Treat social media buzz and actual demand as separate | Face engineers rather than chase attention |
| Set metrics that measure the event's purpose | Do not decide for the numbers alone |
| Drop plans readily | Step up to the plate, and drop plans readily |
| Return to the target and the goal when unsure | Keep ownership of the plan |

## Guidelines for applying the principles

The following guidelines apply these principles to planning.
They apply to any organization that runs events for engineers.

**1. Write down the criteria before planning**

State the target, the goal, and what each of the three parties gains
before choosing speakers or a format. Criteria written in advance give
a fixed point to return to when choices compete.

**2. Interview to gather material, not to hand over the decision**

Ask engineers about the target's situation and needs, which cannot be
learned from articles alone. Prepare your own view first so the
conversation tests it, and keep the final decision yourself.

**3. Ask for other topics before closing an interview**

When a plan does not hold up, ask what else the person is interested
in. Material for the next plan often comes from that last question.

**4. Match the angle to the technology's stage**

For a technology with few results yet, focus on difficulties and trial
and error rather than outcomes. This lowers the bar for speakers and
matches what participants are about to face.

**5. Review against the criteria, not only the numbers**

After the event, compare the result with the criteria written in step
one. Check whether the event stayed on its axis, and record what worked
and what fell short so the next plan can use it.

> [!WARNING]
>
> Methods that put speed first, such as planning a theme within hours of a
> product release, are effective only when freshness is the main value of
> the theme. Applying them to every event lowers quality and moves the
> event away from benefiting all three parties.

## Related pages

> [card] [The role of DevRel](https://lib.findy.co.jp/devrel/engineering-culture.md)
>
> The engineering culture and community structure these principles are
> meant to serve.

> [card] [Online Events](https://lib.findy.co.jp/devrel/online-event.md)
>
> The planning and preparation steps where these principles turn into
> concrete decisions.

> [card] [Technical Editing](https://lib.findy.co.jp/devrel/technical-editing.md)
>
> The other main channel besides events: preparing articles for technical
> media before they are published.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.