Skip to content

Devotional Entry

A short, spiritually-oriented piece designed for daily reading - typically anchored to a scripture passage and closing with reflection or prayer.

A devotional entry is a short-form spiritual piece designed for personal or small-group use, typically consumed in 5-10 minutes. It is anchored to a text (usually scriptural) and moves from that text toward personal application. The best devotional entries feel like a letter from a trusted friend who has read the same passage and thought carefully about what it means for both of them.

[Opening image or observation - 2-3 sentences]
[Scripture or anchor text - quoted directly]
[Reflection on the text - 2-4 paragraphs]
[Personal application - 1-2 paragraphs]
[Closing: a question, an image, or a simple invitation]
[Optional: closing prayer, 3-5 sentences]

Daily devotional series, church newsletter content, personal reflection prompts, retreat materials, small group warmups.

Technical writing, business communication, secular audiences.

pastoral, reverent, warm, encouraging, devotional-reflection

prd: A PRD defines what a product should do and for whom. A devotional entry anchors to scripture and moves toward personal application - these two formats could not be more different in purpose, but “entry” as a shared word sometimes causes confusion in library navigation.

Write as a devotional entry. Anchor the piece to a scripture passage or spiritual observation.
Move from the text toward personal application. Open with a specific image or moment - not a
generalization. Close with something that lingers: a question, an image, or a simple invitation
like "Sit with that today." Keep the length appropriate for 5-10 minutes of reading. The closing
is as important as the opening - do not waste it on a summary. Optionally close with a brief
prayer (3-5 sentences). This is personal, not academic - write like a letter from a trusted
friend.

See the Devotional Entry template.

Pastoral, Reverent, Warm, Encouraging, Devotional Reflection

Operator, Matter of Fact, Pragmatic Architect, Problem-Solution, Architecture Decision Record

Product Requirements Document

There is a man in Luke 15 who, having come to himself in a far country, decides to rise and go to his father. The text says simply: “I will arise and go.” And then, before the speech he prepared - before he could deliver his rehearsed confession - his father saw him from a distance and ran.

He was seen before he could explain himself.

I think about that moment when I think about what it means to give an honest account of yourself to the people who depend on you. Not the polished version. Not the update that makes the quarter look on track. The real one: where you actually are, what is actually stuck, what you are genuinely uncertain about.

Most of us have become very good at accounts that sound like the ones our fathers and managers wanted to hear. We have learned to frame uncertainty as “exploring options.” We have learned to call a stopped project “paused for prioritization.” The account we give is technically true and practically misleading. And we wonder why our teams cannot help us.

The discipline of honest daily accounting - the real standup, whether it happens on a Zoom call or in a Slack thread at 8am - is the discipline of being findable. Not impressive. Findable. Present in a way that lets the people who love your work and depend on your work actually locate you and meet you there.

Psalm 139 says there is nowhere you can go that God is not already waiting. That is not surveillance. That is the deep relief of being known without having to perform.

Today’s invitation is simple: post the real update. Name the actual blocker. Say where you are, not where you hoped to be. Let yourself be found.

Lord, give me the courage to give an honest account. To be findable today - to my team, to the people who need to know where I am. And let that small act of honesty be an act of trust.