What Leaders/Managers Can Learn from The Tech-Wise Family
A manager inherits a team that prides itself on responsiveness. Chat replies land within minutes at any hour, dashboards refresh in real time, and a new tool arrives every quarter promising to remove one more manual step. On paper, the team looks efficient. In practice, fewer people volunteer for the hard, ambiguous project nobody has a template for. Skills that used to get built through struggle, like talking a difficult client down or debugging a problem nobody has seen before, seem to be quietly atrophying while everyone gets faster at everything easy. Nobody set a rule about any of this; habits simply formed around whatever tool made the moment easier. What kind of team is being built when nobody ever decided on purpose?
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Ease is a tool, not the goal of the team
Crouch's core distinction is between what makes life easier and the harder, more meaningful work a team actually exists to do. A leader who treats every convenience as a win, without asking what it costs, drifts toward a team that is fast but shallow. Crouch writes partly from his own Christian conviction that people flourish through meaningful effort rather than mere ease; translated for any team, the point stands alone: convenience is worth having only when it frees people for harder work that matters, not when it replaces the judgment and craft the role actually requires.
Leaders assume any tool that saves time is automatically good management.
Before rolling out a new tool, name the skill it might replace and decide deliberately whether that trade is worth it.
Build boundaries around attention, not just output
Crouch's household boundaries, screen-free rooms and hours, translate into workplace structure: meeting norms, notification defaults, blocks of protected focus time. A leader who never sets these leaves everyone to negotiate their own limits under pressure, which usually means limits disappear. A leader who sets one clear boundary, no laptops in a working session, a real end to the workday's notifications, gives the team permission to protect the deep work that produces good judgment, rather than leaving protection to individual willpower alone.
A boundary announced once and never modeled by the leader collapses within a week.
Pick one team ritual, like a meeting or a daily window, and make it screen-free by explicit agreement.
Let people struggle with the right problems
Crouch treats difficulty as valuable rather than something to eliminate immediately. A manager who reflexively rescues every stuck employee with a shortcut or a quick answer denies them the exact friction that builds real capability. This does not mean withholding support; it means being deliberate about which struggles are worth letting play out a little longer, so a person develops judgment rather than dependence on the fastest tool available.
Leaders confuse withholding help with building character, and people burn out instead of growing.
Before solving a stuck employee's problem, ask what they would learn from working through it one more round.
Keep the conversation about values alive
Crouch's fourth cluster is about sustaining commitments through honest, ongoing conversation and a real willingness to adapt, not rigid rules imposed once and forgotten. A leader who wants a team that uses technology deliberately has to keep naming that intention out loud, checking in as pressures change, and adjusting practices to fit real circumstances rather than defending a policy nobody remembers agreeing to in the first place.
Deadlines and deep work rarely arrive on schedule together. A leader will regularly face a moment where protecting a screen-free block or letting someone struggle a little longer feels like it will cost a deliverable the team cannot afford to miss. There is no clean formula for resolving this; the honest approach is naming the trade-off out loud with the team, rather than quietly abandoning the boundary every time something feels urgent, which teaches everyone that urgency always wins.
Name one thing, honestly
- Which team habit exists only because it was the easiest default, not a deliberate choice? - Where would one protected boundary change what your team is capable of a year from now? - Whose struggle are you rescuing that might actually build their skill?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Before solving a stuck employee's problem, ask what they would learn from working through it one more round.