The Townhouse Transformation: A Realistic Roadmap for Structural Generational Transition
After thirty years of sitting in ERP steering committees—watching companies try to compress an eighteen-month S/4HANA rollout into six months because a VP wanted a "quick win"—I have learned one lesson that applies just as much to the church as it does to the boardroom: the timeline you wish for and the timeline reality gives you are rarely the same number. When I first encountered the Ecclesiological Townhouse Model, written by Dr. Ben Shin and Dr. Sheryl Silzer (Shin & Silzer, 2016), I loved the framework but winced at the four-year "Strategy 4L" timeline (Learning, Loving, Linking, Launching) (J.D. Kim, 2006). In my experience leading and consulting on enterprise transformations, and now pastoring a Chinese immigrant congregation, four years is the floor, not the ceiling, for structural change of this magnitude.
Why Four Years Is a Best-Case Scenario, Not a Plan
In enterprise resource planning work, even a mid-market ERP rollout for a company of 50 to 500 employees typically takes six to twelve months just for the technical configuration, and large enterprises with 500 to 5,000 staff routinely need twelve to twenty-four months (ERP Research, 2022). That is just the system. Getting people to actually trust and adopt the new system, what consultants call "user comfort", takes another full year beyond go-live, according to practitioners who have run large SAP greenfield implementations (Reddit r/SAP, 2025). John Kotter, whose eight-step change model has shaped my thinking as much as any seminary class, states it plainly: short-term wins can appear in six to eighteen months, but for change to sink into the actual culture of an organization, "it can take three to ten years" (Kotter, as cited in Simplifying Processes, 2022; Kotter Inc., n.d.). A church is not a company, but it is at least as relationally complex, and often more so, because you cannot lay off a founding elder who resists the new org chart.
So instead of a four-year Waterfall sprint, I recommend churches plan for a five-to-seven-year phased rollout, structured less like a single Big Bang go-live and more like a phased ERP deployment where each "wave" earns the readiness for the next (Panorama Consulting, 2026).
Year 1 to Year 2: Learning and Discovery (The Requirements Phase)
This maps to what ERP consultants call discovery and design. Except here the "requirements gathering" is theological and relational, not technical. Leaders from both the first and second generation attend joint seminars and study healthy Townhouse case studies such as Seoul Baptist Church of Houston (Shin & Silzer, 2016). Do not rush this. In corporate change work, skipping discovery is the single most common cause of failed transformations; in the church, skipping this phase produces exactly the "Silent Exodus" that the Townhouse Model exists to prevent (Sola Network, 2025).
Year 2 to Year 4: Loving and Piloting (The Configuration and Pilot Phase)
Launch "Prototype Cells," pilot Townhouse units that model shared authority before you ask the whole congregation to trust the new structure. This is the sandbox environment before production go-live. Expect this phase alone to take 18 to 30 months, roughly comparable to what large enterprises spend on design and testing before a full rollout (ERP Research, 2022; Gartner Peer Community, 2022).
Year 4 to Year 6: Linking and Integration (The Phased Go-Live)
Systematically convert traditional "district" or discipleship structures into the new cell system, cutting programs that no longer serve the vision. In ERP terms, this is the phased cutover: legacy systems are decommissioned wave by wave, not all at once, because a full cutover without a stabilization period ("hypercare," in ERP language) is where most transformations break (ERP Research, 2022).
Year 6 and Beyond: Launching and Sustaining (Continuous Improvement)
Full multiplication happens here, and units that outgrow their span of care split to preserve intimacy. This is not a finish line. Just as ERP systems require ongoing patches, upgrades, and governance long after go-live, the Townhouse requires permanent maintenance, which I address below.
Honestly, even this six-year outline assumes a healthy, cooperative Senior Pastor and a congregation without major conflict. Add eighteen to twenty-four months if your church is recovering from a split, a pastoral transition, or significant "Face" conflict, because trust rebuilding always outpaces technical rebuilding.
How Big Does a Church Need to Be to Start?
This is the question every mid-sized pastor asks. Here is my honest, consultant's assessment.
The Oikos unit (Billings, 2011) in the Townhouse Model caps at twelve people for healthy discipleship (Shin & Silzer, 2016). To run even a modest Townhouse structure, you need at minimum two functioning generational or linguistic units, each ideally supported by two to three Oikos groups so that leadership does not collapse the moment one leader burns out. That is roughly a minimum of 50 to 75 people in a committed, discipled community, not counting Sunday attendance, which typically runs two to three times higher than committed core participation.
For reference, the national multisite benchmark states that the minimum viable "launch core" for a new campus or unit is 75 people, with 100 considered the healthy floor (Multiply Vineyard, 2013). Multisite churches that successfully launch new campuses average 850 in total attendance, though that figure reflects full campus multiplication rather than the more modest generational unit-splitting described by the Townhouse Model (Multiply Vineyard, 2013).
Here is the encouraging part. According to the 2020 and 2023 Faith Communities Today (FACT) studies, the median U.S. congregation has only 60 to 70 people in weekly attendance, and roughly 70 percent of American churches have weekly attendance under 100 (Church Consulting, 2025; Lifeway Research, 2021; Hartford Institute for Religion Research, 2023). You are not the outlier. You are the norm.
| Church size | Townhouse readiness | What it looks like |
|---|---|---|
| Under 75 | Pre-launch | Focus on Year 1 discovery and one strong pilot Oikos group before adding structure |
| 75 to 150 | Minimum viable | Two units possible, each fed by 1 to 2 Oikos groups; expect a longer Year 2 to 4 pilot phase |
| 150 to 300 | Comfortable launch | Multiple units with redundancy; matches the healthy floor cited in multisite research (Multiply Vineyard, 2013) |
| 300 and above | Full deployment | Resources exist for parallel units, dedicated Unit Pastors, and children's ministry "lobby" integration |
If your congregation is under 200, you are not disqualified from this transformation; you simply need a longer runway and a smaller initial scope, much like how a small business takes three to six months for a small ERP rollout, while an enterprise takes two to three years (ERP Research, 2022) for theirs. Scale changes the timeline, not the destination.
Phase I: Project Initiation and Stakeholder Alignment
Every ERP project I ran lived or died on executive sponsorship, and church transformation is no different. The Project Sponsor here is almost always the first-generation Senior Pastor, sometimes alongside the founding families to whom he answers relationally, and without that positional blessing the project meets blockers no amount of good planning can clear (Shin & Silzer, 2016).
- Document a clear theological vision for a multi-unit future and bring it to a cross-generational Eshel Bridge Leadership Team (EBLT) for shared ownership (Choi, 2024).
- Implement "Mutual Invitation" so every unit leader, first-generation, English ministry, and youth alike, has structured voice, preventing the quiet attrition researchers now call "Silent Divergence" rather than the older term "Silent Exodus" (Sola Network, 2025).
- Treat this like a project charter: name a target go-live for Phase II, but build in a mandatory readiness review before advancing, the same discipline that keeps ERP go-lives from launching on unstable data (Panorama Consulting, 2026).
Phase II: Resource Mapping and the Five-Category Inventory
Configuration in any system, corporate or ecclesial, starts with an honest and real inventory of what you actually have, not what you wish you had.
- Human resources: identify the elders already informally shepherding peers, your "leaders among leaders" (Croy, 2022; Choi 2024).
- Physical resources: audit sanctuaries, halls, and kitchens for time-slot availability to prevent the double-booking conflicts common to shared-space models.
- Intellectual resources: run a demographic scan of your neighborhood, your "Blue Ocean," to determine whether a new unit should be multiethnic or generational.
- Financial resources: transition from a single mother-church budget toward strategic funding for each unit, while retaining a shared-roof contribution for facility upkeep.
- Spiritual resources: establish a dedicated prayer base, because this model demands a higher tolerance for relational messiness than a traditional single-board structure.
Phase III: Structural Design Using the ODA Framework
Once the inventory is complete, design the units according to the level of intimacy required for discipleship, using the Oikos, Domus, Aula (ODA) typology (Billings, 2011).
- Oikos: house-church-scale ministry capped at twelve, where doing precedes teaching and leadership is distributed.
- Domus: mid-sized gatherings where multiple Oikos units come together for specialized training.
- Aula: the public Sunday celebration expressing full unity even as each unit keeps its own linguistic or liturgical flavor.
Identity branding matters here too. When the English ministry takes a name distinct from the mother church, as Young Nak Celebration Church did relative to Young Nak Presbyterian, it signals to the community that the unit is a homeowner rather than a renter (Shin & Silzer, 2016).
Phase IV: Governance, "Face," and Shared Leadership
This is the hardest module to configure, harder than any ERP security role matrix I ever built, because you are asking a first-generation Senior Pastor to move from Positional Authority to Relational Authority, a primus inter pares posture where he must trust a Unit Pastor's decisions even when they diverge from his own instincts (Croy, 2022). In Asian-American contexts, conflict, such as a facility double-booking, must be handled one-to-one to avoid public Face-loss, with the interconnected network of units providing support rather than mere oversight when one unit struggles.
Phase V: Children's Ministry as the Integration Layer
The Children's Sunday School functions as the "lobby" of the Townhouse, the shared entryway connecting generational islands (Choi, 2024). Recruit "Multicultural Servants," teachers trained in cross-cultural competency, and host events like an International Food Festival to invite the wider neighborhood into the space. The long-term goal is that children who grow up together in this integrated environment form their own adult unit organically, rather than experiencing the Silent Exodus or its subtler modern form, Silent Divergence (Sola Network, 2025).
Phase VI: Monitoring and Key Performance Indicators
You cannot manage what you do not measure, a lesson every ERP steering committee learns the hard way.
- Distribution of storytelling: if only the pastor is speaking, the model is failing; success looks like members genuinely caring what a brother or sister has to say.
- Intercultural Development Inventory (IDI): use this validated instrument to track whether leadership's cross-cultural competency is actually improving over time. (Choi, 2024)
- Intimacy and voice: monitor small-group size; once a unit exceeds twelve, it risks reverting to a big-church program and losing the very intimacy the model exists to protect (Croy, 2022).
An Architecture of Holy Temporariness
The Ecclesiological Townhouse Model is, by design, transitional architecture. A homeowner eventually outgrows a townhouse as the family expands, and a church is a living organism, not a fossilized institution. If your congregation is under 200, do not read the multi-year timeline above as discouragement. Read it as what any honest consultant tells a client before a major systems change: the cost of skipping discovery, rushing configuration, and forcing an artificial go-live date is always higher than the cost of a realistic runway. Smaller churches actually carry an advantage that large enterprises envy: agility. Smaller churches have fewer stakeholders, which means faster consensus once trust is built. Start small, start honest about your true numbers, and give this transformation the years it actually needs.
References
Billings, B. S. (2011). From house church to tenement church: Domestic space and the development of early Christianity. Journal of Theological Studies, 62(2), 541–569. https://doi.org/10.1093/jts/flr106
Choi, H. B. (2024). Growing the multicultural church through children’s ministries: The transformation of a Korean congregation [Doctoral dissertation, Boston University]. OpenBU. https://hdl.handle.net/2144/48167
Church Consulting. (2025, May 28). Rethinking the value of the smaller church, part 1. https://churchconsulting.org/rethinking-the-value-of-the-smaller-church/
ERP Research. (2022, September 27). ERP implementation timeline: How long? https://www.erpresearch.com/en-us/blog/erp-implementation-time
Gartner Peer Community. (2022, January 13). What is the typical time frame for an ERP implementation? https://www.gartner.com/peer-community/poll/typical-time-frame-erp-implementation
Hartford Institute for Religion Research. (2023, January 17). Fast facts on American religion. Hartford International University. https://hirr.hartfordinternational.edu/fast-facts-on-american-religion/
Kim, J. D. (2006). A strategy on the application of cell ministry as a model of a healthy immigrant church [Doctoral dissertation, Liberty Theological Seminary]. Scholars Crossing. https://digitalcommons.liberty.edu/doctoral/1396/
Kotter Inc. (n.d.). The 8-step process for leading change. https://www.kotterinc.com/methodology/8-steps/
Lifeway Research. (2021, October 20). Small churches continue growing—but in number, not size. https://research.lifeway.com/2021/10/20/small-churches-continue-growing-but-in-number-not-size/
Multiply Vineyard. (2013). 125 tips for multisite churches and those who want to be. http://multiplyvineyard.org/
Panorama Consulting. (2026, July 1). How to approach OCM in phased ERP implementations. https://www.panorama-consulting.com/erp-change-management-phased-implementation/
Reddit r/SAP. (2025, November 13). How long did it take for your team to get comfortable with a new ERP? https://www.reddit.com/r/SAP/comments/1ow747i/
Shin, B. C., & Silzer, S. T. (2016). Tapestry of grace: Untangling the cultural complexities in Asian American life and ministry. Wipf and Stock
Simplifying Processes. (2022, March 14). Leading change: An overview of Kotter's eight stages. https://www.simplifyingprocesses.com/blog/leading-change
Sola Network. (2025, October 24). From "Silent Exodus" to "Silent Divergence." https://sola.network/article/from-silent-exodus-to-silent-divergence/

Another challenge these immigrant churches also typically encounter is the short stay of pastors. Unless a pastor is willing to shepherd the congregation for 7 or more years, it makes any plans that require a long period to complete almost impossible to accomplish. As a pastor leaves and another is hired on board, typically the new pastor comes with perhaps a different vision or passion and then the members are left with repeating the discovery phase over and over again.
ReplyDeleteThe tenure of a pastor/leader, for the most part, depends on how well the church and he can work together. Many pastors are there for a reason or a calling. If the church is actively denying that work or calling to come to fruition, many will leave. If the church will not come along with the necessary transformation, there isn't a whole lot the pastor can do.
ReplyDelete