B1 New Feature Guidelines
B1.church is church management software for the work a church already does: people, groups, serving, check-in, attendance, giving, communication, lessons, and the church's website. We add to that often. We also say no, including to ideas that would help the church that asked.
These are the questions we use. A new feature has to fit them. We make exceptions, one request at a time. An exception is a decision about that request. The guideline stays in place for the next one.
If something we already offer is broken, we fix it. This list is for new behavior.
1. It belongs in church management
We add features that help a church do the work B1 is for. A different kind of product, such as accounting, payroll, or inventory, falls outside that.
2. It leaves room for people to participate as they are able
B1 should make ministry easier to organize. Records a church needs for care, for scheduling, and for the books stay available to the people who need them. We are careful about features that would score people, rank them, or follow up on how much they serve, give, or attend. Participation stays voluntary.
3. Churches that do not need it can ignore it
A feature that only a few churches will use should stay out of the way of everyone else. A setting that is off until a church turns it on, and that changes nothing for other churches, can go in.
4. Prefer a way the product already offers
When a screen, an export, a print, or a copy already does the job, we point people there. Another control for the same job makes the product harder to learn.
5. Add to something we already have
A small addition to an existing page is easier to live with than a new area of the product. We look for a place the request already fits before starting something new.
6. Keep the product simple to understand
Each new kind of information is something every church has to learn and keep. We would rather use information we already store. A new field needs a clear reason. A new set of data, or the same special case repeated across the product, is a reason to pause. When that is what the idea requires, we decline it. A smaller version that still needs that complexity gets the same answer.
7. Keep one task in one place
A task should have one place to do it. We avoid splitting a single job across tabs or a second view of the same page. Someone should be able to open the page and finish the job there.
8. Every setting is a lasting cost
Each setting is a behavior we keep, test, and explain. It shows up for the person administering the church, and the code has to account for it wherever that behavior appears. "Just add an admin toggle for..." sounds like a simple solution to many problems, but there is a real cost for each admin toggle added to make something behave a different way.
We add one when a church genuinely works differently and one switch describes that difference. A preference or a small variation can stay the shared behavior. A short list of obvious settings is easy to administer. As the list grows, the product gets harder to maintain and harder to configure.
Exceptions
These are meant to be general guidelines, not hard rules. There are often good reasons to make exceptions and we will do so.
