A framework for building technology that serves human flourishing. Technology should make patterns visible for human action—not automate decisions away from us.

Applied Humanism asks how the things we build actually feel to use, and whether they leave people more capable or less. It emerges from thirty years in technology, perspectives shaped by Singapore, Tokyo, San Francisco, and Hong Kong, and the persistent observation that implementations rarely consider their phenomenology for actual users.

Three Questions

How do we learn?

Understanding how people actually acquire understanding—not how systems assume they do.

How do we think together?

The patterns and practices that enable groups to become more than the sum of their parts.

How do we gain agency?

Building technology that expands human choice rather than circumventing it.

Patterns

Recurring concepts and frameworks. A vocabulary for talking about technology that serves human flourishing.

All patterns →

Context shapes meaning. The pathway to engagement shapes what you find.

Culture as filter means that how you arrive at something changes what it is for you. The same content, reached through different pathways, carries different meaning. Context isn’t just packaging—it’s part of the message.

This has implications for design: you can’t just put content out there and assume it means the same thing to everyone. The filters people come through—their culture, their context, their pathway—shape the meaning they find.

Resistance as design principle. Optimizing for meaning, not volume.

Deliberate friction introduces intentional resistance to slow down, create space for reflection, or ensure engagement is genuine. It’s the opposite of frictionless design—but not because friction is good in itself.

The value of friction is in what it enables: pauses that create thinking, effort that creates ownership, delays that create anticipation. Friction is a tool, not a goal.

Asking how things actually feel to use.

Applied phenomenology means investigating experience rather than just behavior. For technology, this means asking not just “does it work?” or “do people use it?” but “how does it feel to use? What is the experience actually like?”

This is the through-line of Applied Humanism. Technology should be evaluated not just on what it does, but on what it’s like to live with. Does it leave you feeling more capable or less? More human or less? More connected to your purposes or more disconnected?

The answers aren’t always what the metrics say.

Meaningful results over scale. Clear benefits over speculation.

Bounded experiments prioritize depth over breadth. Instead of building for everyone, build something that works completely for a specific context. Prove the concept before scaling.

This runs counter to typical tech culture, which prioritizes growth above all. Bounded experiments insist on proving value before expanding scope.

Share the journey and the struggle, not just the destination.

A trophy shows you what someone achieved. A map shows you how they got there. Both have value, but they serve different purposes. Trophies inspire; maps enable.

Map vs trophy is a choice in how you share work. Showing only results (trophies) makes the process invisible. Showing the journey (maps) gives others something they can follow, adapt, and build on.

Applied Humanism prefers maps. The point isn’t to impress, but to enable.

Proof of systematic thinking. Portable and referenceable.

When a pattern has a name, it becomes visible and discussable. Named mechanisms show that you’ve thought systematically about how something works—and they give others a way to refer to that thinking.

This patterns vocabulary is itself an example. Each pattern has a name, making it portable—you can reference “deliberate friction” without explaining it every time. The names accumulate into a vocabulary for talking about technology that serves human flourishing.

This work comes from Canada—currently Victoria, British Columbia. The thinking has been shaped by years in Singapore, Tokyo, and Hong Kong, by a stint in San Francisco during the first dot-com era, and by collaborations across the globe.

Applied Humanism isn't thought leadership. It's applied phenomenology for technology: asking how things actually feel to use, whether they expand or diminish human capability, and what it would take to build differently.

More about →

Trevor Wingert

Victoria, BC, Canada

If this work resonates—or if you're building something that asks similar questions—I'd like to hear from you.

hello@appliedhumanism.ca →