Ten principles for product teams

Build tools that serve faith and relationships.

A Bible reader, prayer app or AI assistant shapes more than a task. It can influence whom people trust, how they practise faith and where they turn for help.

These ten principles connect Christian calling with the decisions a team makes before shipping.

Explore the ten principles

Berlin’s TV Tower reflected in the grid of a glass facade.

Start with a decision your team is making. Ask what good it should serve, who could be burdened by it and what you need to learn from the people affected. The five areas below help you examine Scripture, the person, their practice, their relationships and your responsibilities as makers. Read the theological grounding or compare design options.

The Word

What do we put in front of people as God’s word, or about it?

Keep the Word distinct, and teach it truly.

Every screen teaches, and those who teach are judged more strictly. Let readers always tell Scripture from our words, and our words from a machine’s: label every heading, note and answer, show the traditions where Christians differ, and keep a verse inside its passage.

Never speak for God.

An app may quote, explain, pray the church’s prayers and point. It must never pronounce, promise or plead in God’s name, nor let a persona or a machine take the place of a person or of God. The Lord’s Prayer, a psalm or a written liturgy are the church’s words, offered as such; the persona that claims a relationship, and the promise that claims God’s answer, are not ours to make.

The person

How do we receive the one holding the phone?

Design for the most vulnerable first.

Design first for the person most likely to be hurt: in crisis, grieving, abused, scrupulous, new to faith, hurt by a church, or, where an app serves them, a child. Help comes before features, verses or answers, and a way to a person is never behind an account, a limit or a paywall.

Welcome before you ask, and guard what is told in confidence.

“Come and see.” Let people reach what they came for before asking anything, ask only for what serves them when it does, and treat what they tell you to pray as holy ground: never marketing data, never stored by default.

The practice

What do we ask of their time, attention and money, and when do we stop?

Feed the flock, not on it.

Attention, time, devotion and money are entrusted, not harvested. Ask for them honestly, never through guilt, fear, urgency or a promise: no streak warnings marked urgent, no “we miss you” in a persona’s voice, no tier chosen for the giver.

Make room for rest, and say when it is enough.

The Sabbath was made for people. A faithful product sometimes asks for less: it ends a session, keeps the night quiet, stops asking when the need is met, as Moses stopped the offerings when there was more than enough, and lets itself end when its work is done.

The people

Where do we send them, and what do we claim to have grown?

Send people to God and to one another.

The app is a means, never the destination. Judge it by where people go when they close it: to Scripture, to prayer, to a church, a group, a friend. For someone isolated or hurt by a church, an online community may be the safe place; the bridge must lead somewhere chosen and safe.

Plant and water; leave the growth to God.

Measure what serves the person and the task: usability, understanding, burden, harm. Never score a soul, never present usage as spiritual fruit, and never claim the fruit as yours.

The makers

Who are we becoming as we build?

Make it well, as an offering.

God filled Bezalel with skill for his work. Excellence, accessibility, beauty and care are how we love God and the person on the other side of the screen. “It’s for ministry” is never an excuse for careless work.

Hold it with joy and trembling, before God and others.

Rejoice in the work and take its weight: pray for the people who use it, invite those who can say no early, confess mistakes plainly, and tend what you release.

Each principle, with its Scripture, tradition, what it rules in and out, and questions to test a design: patterns.missional.design/principles.

The app is a means, never the destination.

Judge it by where people go when they close it: to Scripture, to prayer, to a church, a group, a friend.

Exploitative, ethical, redemptive.

The three ways are the work of Praxis, whose Redemptive Frame calls the redemptive way “creative restoration through sacrifice”. We read it for apps whose subject is God, where the first temptation is not only to use people but to use God’s name. FaithTech’s Playbook makes the same turn with reckless, responsible and redemptive technology. This guide applies both frameworks to the theological and pastoral responsibilities of spiritual apps.

Exploitative

Praxis: “I win, you lose”

The app takes the place. It borrows God’s voice to bring people back, sells access to prayer or a promise of blessing, keeps confidences as data and counts faith as usage. Name it. Refuse it.

Ethical

Praxis: “I win, you win”

The app keeps its place: safe, honest, accessible, lawful, careful with data and time. This is the floor and a gift of common grace, but it is not the goal.

Redemptive

Praxis: “I sacrifice, we win”

The app points beyond itself. It withholds claims it could make on attention, data, money and trust, tells the truth about itself, and is glad when people close it to go to God and to one another.

Three things worth holding.

The ten overlap and sometimes pull apart. Some tensions must be held, not solved.

Rhythm vs. pressure: Feed the flock, and make room for rest. A spiritual life needs rhythm, but the moment a rhythm becomes an enforced expectation it turns into pressure. Invite people into rhythm, and after silence ask once, then stop.
Community vs. starting alone: Send people to one another, and design for the most vulnerable first. Many begin alone, and some were hurt in a church. Build bridges that invite toward community rather than making it the price of entry.
Devotion vs. a voice that is not God’s: Never speak for God, and welcome before you ask. Offer the church’s prayers as the church’s, keep a way to a person first, and let no persona say it will pray.

Diagnostic questions.

Use these to evaluate any feature, campaign, or design decision before it ships.

01Does this serve growth in faith, or only the usage numbers?
02Freedom or anxiety?
03Would we put our own name under this sentence, or are we borrowing God’s?
04Who is the most vulnerable person likely to use this today, and what will they see?
05If a user had a spiritually dry year, would they feel welcomed back or judged?
06If people developed deep communion with God and no longer needed the app, would we celebrate or mourn?

Want to apply the framework?

Use the principles to examine a product decision with your team, then explore the practical options in the pattern library. Theological and pastoral review of this draft is pending; contributions from reviewers are welcome.

Use the principle worksheet Read the principles with sources Get in touch About the author

Need to understand your context?Use the canvas with your team to listen, clarify your missional identity and shape a next step.Open the canvas Ready to compare concrete options?Explore examples and trade-offs for Bible reading, prayer, community and AI.Explore the patterns