A Practical Guide to the TEMPLE Model: From Launching an Internal Community to Sustaining It

Key points (30 seconds)

- Conclusion: Community operations become reproducible when designed around the six TEMPLE pillars: Theme, Environment, Members, Persistence, Local, and Evolution

- We organized the knowledge from 7 years, 165 events, and 615 members of Kyoto community Miyako de IT into those six pillars

- An internal community begins moving when the pillars are translated into five steps: T, E, M, P, and L

- Each section includes practical knowledge for venue design, turning participants into supporters, continuity, external collaboration, and evolution

- Failures converge on two patterns: disappearing after three months and becoming an insular group of fixed participants

Launching internal communities is increasingly discussed in business development, HR, and organizational development at operating companies. Objectives differ—exploring new businesses, learning across technical domains, sustaining younger employees' engagement, or creating recruiting contact—but the shared issue is creating a setting for learning and connection beyond organizational silos.

Common failures include stopping within three months and becoming insular as the participants become fixed. This article systematizes the knowledge gained by operating Kyoto-based Miyako de IT for 7 years, 165 events, and 615 members through the six TEMPLE pillars. It explains the overall model while attaching usable field practices to each pillar. Internal communities can more readily obtain structural support through HR systems, budgets, and managerial approval, which can lower the launch barrier.

---

1. Why an internal community is needed

The limits of siloed organizations

Operating companies are divided vertically by business unit, function, and region. This speeds decisions but structurally makes cross-functional learning, information sharing, and personnel exchange less likely. In organizations with more than 1,000 people, not knowing what the neighboring department is doing becomes routine.

An internal community creates a horizontal connection across those silos. Regular gatherings across business units around a technology, interest, or career issue produce another network inside the organization.

Effects on soft indicators

A voluntary learning setting separate from official duties may positively affect younger employees' engagement and retention, although each organization must measure causality. In new business, cases have also been observed where a personally introduced theme connects with someone in another department and begins moving as a project.

A structure that continues as a community, not merely a study session

A one-off study session and a community must be distinguished. The former centers on one-way transmission from instructor to participants, and relationships end afterward. A community centers on continuing relationships among participants, preserving connection between events. The six TEMPLE pillars in the next section design that continuity from the outset.

---

2. Five steps learned from operating an external community

Miyako de IT began with two people in 2019 and by 2026 had grown to 615 members and 165 events. It uses Kyoto's regional character through monthly events at varied venues including temples, ochaya teahouses, and university campuses. TEMPLE organizes those 7 years of operating knowledge into six pillars.

The five launch steps correspond to the first five pillars, T/E/M/P/L. Evolution sits outside the steps as the perspective for development after launch.

Following them in sequence creates the minimum structure of a continuing internal community within six months of the first event.

---

3. Step 1: Clarify the theme (T)

Can you state why people gather in one sentence?

The greatest reason an internal community fails to take root is an ambiguous theme. “A place to promote DX” or “a place to encourage internal innovation” is too abstract for participants to make personally relevant.

The theme must be specific enough to state in one sentence: “a place to bring together manufacturing AI-use cases and organize them for company-wide deployment,” “a place for engineers in their twenties to try new technologies after work,” or “a monthly place to share seeds for new businesses across business units.” A listener should be able to decide whether they should attend.

Resolution changes the reason to participate

Miyako de IT can state its theme in one sentence: “create a connection between Kyoto IT and the local context.” Its clarity lets web engineers, startup executives, and local-government staff all decide it relates to them. “Interaction among company engineers” is not enough for busy staff. Translating it into visible activity and a goal—such as gathering ten AI-use cases from business units in six months and designing cross-company deployment—communicates why participation matters.

Choose an axis: business issue, technology, career, or location

• Business-issue axis: New-business exploration, competitor analysis in a domain, or extracting successes for wider deployment
• Technology axis: Internal cases for a stack, catching up on new technology, or standardizing engineering practices
• Career axis: Early-career employees, women engineers' careers, or transition into management
• Region/location axis: Connecting regional offices or headquarters and branches

Choose the intersection of the organizer's interest and an organizational problem. A theme the organizer does not personally care about will not last six months.

---

4. Step 2: Select the venue and format (E)

Is an internal meeting room really suitable?

It costs nothing, has equipment, and minimizes travel, but it has a major weakness: ordinary work mode does not switch off. In the same room, chair, and fluorescent light, people retain their everyday work posture, making cross-functional dialogue, honest sharing, and new ideas less likely.

The message carried by a venue

A venue has a message. At a temple, Miyako de IT participants concentrate more deeply; at an ochaya they discuss IT in Kyoto's cultural context; at a university campus the setting adds academia–industry collaboration and education. A priest speaks, an okami provides the venue, or a professor co-plans the event. Because the venue connects to the theme, participants experience the worldview each time. This “venue brand” makes the physical setting embody the theme.

Internal venue options

• Executive-floor lounge: An ordinarily inaccessible setting creates distinction and lowers psychological barriers
• External rental space or café: Makes it easier to exit work mode
• Company cafeteria or break area after hours: Food encourages relaxed conversation
• A client or partner office visit: Also creates an external connection
• A one-day off-site retreat: Enables deep discussion at milestones such as every six months

Combine them according to budget and scale. At minimum, consciously choosing somewhere other than the usual meeting room shapes the community atmosphere.

Venue-brand example: Miyako de IT at a temple

Miyako de IT has met continuously at Butsugenji in Nakagyo Ward, Kyoto, since April 2024, regularly bringing laptops into the main hall. Three factors make the temple work. First is quiet: the main hall admits little outside noise. Second is the ritual of switching modes: passing through the gate, removing shoes, and entering the hall releases work mode. Third is communicability: “writing code in a temple” itself has appeal and creates a connection between region and IT. An internal community can likewise turn the venue into a brand by connecting the theme to an experience possible only there.

---

5. Step 3: Design the first session (M)

Six to ten people is realistic

With fewer, discussion does not form; with more, each person cannot speak. Miyako de IT had seven people at its first event, three at its second, and seven at its third. Fluctuation is normal early on; continuing without forcing growth ultimately supports retention. Pursuing a large first event upsets the balance between organizer burden and participant satisfaction.

Four roles: organizer, regular, first-timer, and partner

• Organizers, 1–2: Design the theme and operate the event
• Regulars, 2–3: Attend every time and shape the atmosphere
• First-timers, 2–3: Bring new perspectives
• Partners, 1–2: Guests from another department, outside company, or affiliate

Only regulars creates insularity; only first-timers creates no continuity; no partners creates no outside connection. Deliberately balancing the roles is central to the first session.

Participatory and audience formats

Alternate formats where everyone speaks—workshops, lightning talks, and discussions—with audience formats such as lectures and panels. Early sessions should center on full participation because audience formats require speakers and make participant relationships less likely. Combine them after three to six months of relationship building.

Creating psychological safety

• Always provide check-in time: In the first ten minutes, everyone shares a brief update
• Explicitly remove job titles: State that titles are not used and everyone is addressed by name
• Clarify records: Confirm whether minutes exist and their internal sharing scope
• Do not introduce negative evaluation: Receive a comment before responding rather than criticizing it

Repeating these steps teaches participants that the setting is safe for honest conversation.

Design the second visit: support and retention

The most overlooked Members mechanism is encouraging a first-timer's second visit. Attrition is highest immediately after the first visit. In a company or region with a limited population, continually recruiting newcomers exhausts itself in months, so the design must make people want to return. Miyako de IT's operating figures put its repeat rate at about 45% as a 2026 estimate. Practices thought to support it are:

• Lower the participation barrier: Keep fees free to a few hundred yen, while not always making them completely free; even a small payment reinforces the decision to attend
• Assume solo participation: Say it is welcome, have the organizer make introductions, and never leave someone without a place
• Speak to everyone in the first five minutes: A 30-second reception conversation about name and purpose determines whether they feel welcomed
• Give next-event information before departure: Along with telling them, offer a notification path such as group registration or a calendar invitation
• Explicitly permit late arrival and early departure: Removing the requirement to attend end to end lowers the barrier
• Do not exclude by skill: Individual-work sessions keep skill differences from harming the experience

Measure the share of first-timers who return later, the share of all participants who are repeaters, and the share who bring a colleague.

---

6. Step 4: Operate repeatedly (P)

Six months creates establishment

The main challenge is operating without stopping for six months. Three events remain indistinguishable from a one-off; six monthly events create an expectation that another will follow. At Miyako de IT, self-direction began after the seventh event, when participants started bringing suggestions for speakers and venues.

Use a monthly, fixed weekday and time

Weekly is too burdensome; every other month lets relationships cool. Fixing a schedule such as the third Thursday allows participants to block time six months ahead. Re-negotiating every date instead leaves more than half unable to attend.

Reports and follow-up

1. Within 24 hours: Thank everyone, share photographs, and announce the next event

2. Within one week: Share minutes and presentation materials

3. Two weeks later: Preview the next theme and recruit speakers

4. One week before the next event: Send a reminder and confirm attendance

Repeating the cycle keeps the community present in participants' minds.

Distribute roles and remove organizer dependency

Persistence depends on not concentrating support roles in one organizer. Unless roles are distributed within six months, the community stops when that person transfers, becomes busy, or leaves. From the third event, assign regulars:

• Venue: Booking and setup
• Records: Minutes and photographs
• Communications: Next-event announcements and recruitment
• Outreach: Inviting and connecting first-timers

The organizer may initially do everything, but the six-month goal is transferability. After a year of personalization, systematization rapidly becomes more expensive.

Three principles that prevent exhaustion

• Do not stop the monthly baseline: Some months may have more events, but always hold one. Predictability itself creates trust
• Do not set participant count as a KPI: A ten-person target makes an eight-person event feel like failure. Three people can have a deep conversation
• Do not turn events into an obligation: Obligation removes enjoyment. Use the co-working session as the base and add networking or lightning talks only in months with capacity—a “base + 1” design

The walls at 10, 30, and 100 events

Based on Miyako de IT's experience, after ten events—about one year—people recognize the community is not accidental. Around 30 events, or two to three years, it becomes “that community” locally or internally and receives joint-event requests. Beyond 100 events, or roughly five to six years, credibility itself becomes an asset and venue owners, governments, and companies regard it as safe. Miyako de IT's 165 events underpin continuing use of Butsugenji and its external collaborations.

---

7. Step 5: Expand connections (L)

Create connections beyond the company

A community closed inside the company tends within six months to one year toward insularity, stagnation, or narrowed vision. External connections include other departments, affiliates, clients, external communities, regional organizations, universities, and local governments.

Connect with other departments, affiliates, the region, and universities

• Guest talks: Invite one person from another department or affiliate each time
• Joint events: Hold one with another community every six months
• Visits: Visit a client, university, or regional organization's office or facility
• Cross-posting: Have a company member speak to an external community, and vice versa

Miyako de IT maintains connections with regional hubs including Kyoto City Hall, Kyoto University, Kyoto Research Park, and Kyoto Economic Center. Participants understand that attending offers an overview of Kyoto's IT activity.

Three barriers external collaboration breaks

First is venue: an invitation to use a partner's space removes monthly searching. Second is recruitment: a joint event adds participants from the partner's network. Third is trust: moving from an unknown gathering to a community jointly organizing with a recognized organization raises credibility with companies and governments.

Finding and maintaining partners

Miyako de IT initiated every collaboration itself. Four entrances are asking owners of places already used—cafés, temples, or machiya—directly; explaining the work to a regional industry-support institution as connecting technical talent; cross-referring with a community on another theme; and approaching universities committed to academia–industry collaboration or regional contribution about shared space. Three principles sustain the relationship: design a benefit for the partner, such as awareness for the venue, student-career contact for a university, or recruiting contact for a company; briefly report reactions afterward and communicate with the venue name; and do not force a higher frequency. Miyako de IT currently collaborates with 14 organizations and institutions, including Butsugenji as a venue, Kyoto Chiesangyo Sozonomori on networking events, Digital Nomad Kyoto on co-working sessions, and Taisho University Kyoto Academia as a venue.

Evolve from independent operation into a hub

With several external connections, the internal community becomes a hub: an apparatus relaying people, information, and project opportunities between inside and outside, producing several kinds of value unavailable to a closed group.

---

8. The Evolution perspective

Three layers: individual, community, platform

• Individual layer: The organizer launches it as a personal interest and activity
• Community layer: Roles and continuity become established and it is recognized as an organization
• Platform layer: It becomes embedded in multiple business processes as a setting for business, recruiting, and regional contact

The usual route moves from individual to community in six months to one year and reaches the platform layer in two to three years.

Evolving activity formats: contact, relationships, and value

Alongside organizational maturity, activities evolve through three levels. The contact level—co-working sessions and free events—aims to meet, lowers barriers, and builds the population. The relationship level—networking, lightning talks, and themed study groups—aims to connect, helping acquaintances understand one another's interests and work. The value level—hackathons, joint development, and recruiting contact—aims to build together and turns relationships into projects. At Miyako de IT, members who met at a co-working session formed a team and won the HACK+2023 Grand Prize. Connecting these levels in order is what evolution means; skipping the order prevents establishment.

Clear traps are remaining only a place to work because of attachment to the co-working format; rushing into commercialization before relationships form and driving members away; and making one organizer the bottleneck. Keep the base while gradually adding the next level.

Functions at the platform layer

• Finding business seeds: Discussion can trigger a new project
• Creating recruiting contact: Relationships with invited candidates may positively affect an employment decision
• Deepening client relationships: Contact outside ordinary work can expand project opportunities
• Connecting to region and society: External recognition through CSR and regional contribution
• Developing and selecting internal talent: Active participants may be appointed to important business-unit roles

These do not appear overnight; they emerge after the five steps through continued operation with Evolution in view.

The evolution observed across 7 years and 165 events

Miyako de IT also followed these layers: the first year was Tomohiro Iida's individual interest; years two through four established role sharing and monthly events as a community; from year five it reached the platform layer as a collaboration base for regional companies, governments, and universities. Internal communities can use this pattern as a map beyond the five steps.

---

9. Failure patterns and countermeasures

Pattern 1: Nobody is clearly committed

The theme is decided, but the operational center is not. Several people volunteer in a launch meeting, yet scheduling and venue booking float without ownership and the effort disappears before the first event. Missing pillar: M. Name 1–2 organizers and 2–3 prospective regulars and document their responsibilities before the first event.

Pattern 2: Organizer dependency

The organizer holds everything and roles remain undistributed after the third event. Missing pillar: P. Transfer the Step 4 roles to regulars within six months.

Pattern 3: Becoming a series of one-off events

Every event has a different theme and participants, with no connection between them. Missing pillars: P + M. Fix the monthly schedule and design regulars' roles from the start.

Pattern 4: Shallow KPIs

Only participant count is measured, not essential indicators such as new businesses, recruiting effects, or improved attrition. The budget is cut after six months because no effect appears. Missing pillars: L + Evolution. Set several KPIs at launch on the premise of reaching the platform layer in three years.

---

10. Diagnostic sheet: five questions

Answer Yes or No. If three or more answers are No, revisit the missing pillars.

• Q1. Can the theme be written in one sentence? (T)
• Q2. Have monthly events continued at the same venue, weekday, and time for at least three months? (E + P)
• Q3. Are at least three people other than the organizer assigned explicit roles? (M + P)
• Q4. Is there recurring contact with another department, client, external community, or regional organization? (L)
• Q5. One week before the next event, does the organizer broadly know expected attendance? (P)

---

11. Conclusion

Knowledge from external communities makes internal communities easier to launch. Following T, E, M, P, and L produces a minimum structure within six months. Beyond them, Evolution offers a route from individual to community to platform, where the community becomes a combined apparatus for business, recruiting, and regional contact.

The most important early action is designing with all six pillars in view. Adding pillars later requires changing already-fixed operating patterns and greatly raises the difficulty. Keep all six in view from launch and execute the five steps steadily.

---

Related articles

• Founder profile: Tomohiro Iida
• TEMPLE Model Hub: A Regional Community Strategy Built over 7 Years and 165 Events
• TEMPLE-T: Designing a Regional Community Theme
• TEMPLE-E: Building a Venue Brand
• Seven Common Community-Operations Failures
• For People Afraid of Engineer Meetups

---

The six TEMPLE pillars, five steps for applying them to your company, and the diagnostic sheet are detailed in “The TEMPLE Model: A Community-Operations Framework Built over 7 Years and 165 Events.” Companies considering an internal community, business development, or organizational development are invited to download and use it.