Architecting for Presence: Restoring Sensory Experience in Digital Systems
Has Silicon Valley been building the wrong things? A counterintuitive cost of convenience
I recently read Ian Bogost’s forthcoming book, The Small Stuff, which frames a subtle but powerful shift: many everyday interactions have been “dematerialized” – stripped of sensory texture and bodily engagement – in the name of convenience. The point isn’t Luddism; it’s a design and architectural question for anyone who builds systems, services, or public infrastructure: what do we lose when we optimize only for speed, automation and invisibility?
The signal in one paragraph
Bogost’s diagnosis is simple and useful: a long, incremental drift toward automation and efficiency has reduced opportunities for embodied experience. The consequence shows up in trivial places – restroom sensors that don’t work, the loss of stick-shift driving – but these micro-experiences aggregate into measurable cultural and individual effects.
Why this matters to architects and product leaders
As a Chief Software Architect, I read this not as a nostalgia piece but as a strategic design brief. Modern enterprise and public systems too often treat human interaction as a latency to be removed rather than a channel to be designed. That mindset produces five architectural risks:
-
Outcome-only metrics. Systems measure completion time, throughput, and error rates, but not meaning, agency, or lived satisfaction. These are hard to track, but they determine long-term adoption and trust.
-
Invisible failures. When systems become “invisible”, degraded behavior (broken sensors, wrong defaults) becomes opaque – users feel confusion or loss but cannot diagnose or compensate. Observability has to include user-facing visibility, not just logs.
-
Monolithic automation debt. Over-automating every touchpoint creates brittle flows that break badly outside of expected conditions. Manual fallbacks and human-in-the-loop controls are not regressions – they are resilience patterns.
-
Erosion of trust and agency. If every interaction is delegated to an algorithmic black box, people lose control and the opportunity to learn, rehearse, or feel competent.
-
Cultural mismatch in public systems. Digital Public Infrastructure (DPI) that only optimizes for scale and speed can inadvertently erode social networks and local practices that carry value beyond transactional efficiency.
Design levers you can apply today
-
Recalibrate metrics: supplement completion metrics with qualitative signals – micro-surveys, friction heatmaps, and task-meaning assessments. Track “why the user did this” as much as “whether they did it.”
-
Design visible automation: make automation reversible and transparent. Show the decision the system made, let a user override it, and log that interaction as a first-class event.
-
Intentionally preserve sensory moments: in product flows, identify micro-interactions that confer meaning (rituals, confirmations, tactile feedback) and protect or enhance them rather than remove them.
-
Adopt graceful degradation: ensure an explicit manual path for common flows. Offline-first and edge-capable architectures help preserve continuity and the possibility of embodied action.
-
Use friction as a feature, not a bug: reframe friction as an affordance where it improves comprehension, consent, or safety – e.g., a short pause to confirm a financial transaction or a tactile cue when handing control back to a human.
A pragmatic India parallel (brief)
This debate is relevant to DPI builders too. India’s UPI and identity systems dramatically expanded access by removing friction – a transformative win. The lesson is to pair scale with local agency: enable community-facing touchpoints, human escalation options, and visible audit trails so the digital layer augments rather than erases civic experience.
Takeaways for CTOs and product leaders
- Optimize for experience, not only outcome.
- Instrument the human experience as an observability signal.
- Keep human overrides and tactile fallbacks as resilience patterns.
- Treat “invisibility” as a design choice with trade-offs – document and review it.
- For public systems, balance scale with local, human-centered touchpoints.
Closing thought
Convenience has been an engine of inclusion and productivity – but convenience without craft strips the world of texture. As architects and builders our job is not to stop progress, but to design progress that preserves the human moments that make systems worth using.
About the Author: Sanjeev Sarma is the Founder Director and Chief Software Architect at Webx Technologies. With a core focus on Generative AI integration, Cloud-Native Scalability, and Enterprise Software Architecture, he has spent over two decades driving digital transformation across Northeast India and beyond. Beyond his corporate leadership, Sanjeev is deeply invested in shaping the future of the IT industry. He serves as an Industry Expert on the Board of Studies for Assam Don Bosco University’s School of Technology, advises state technology committees, and actively mentors emerging tech startups at STPI. He brings a unique, dual perspective of high-level enterprise execution and future-ready academic curriculum development.
