# Blog · Lokesh Saini

> Canonical (HTML): https://www.lokeshsaini.com/blog
> Markdown twin of the page above. Contact: hi@lokeshsaini.com · Last updated: 2026-09-14
> Profile: https://www.lokeshsaini.com/llms.txt · API: https://www.lokeshsaini.com/api/portfolio · Resume: https://www.lokeshsaini.com/resume/Lokesh_Saini_Resume.pdf

- [Designing With a Restraint Budget](https://www.lokeshsaini.com/blog/designing-with-a-restraint-budget) (2026-09-14): A greyscale visual system with semantic color reserved strictly for status. One constraint that did more for coherence than any palette.
- [Designing the Thing That Outlives You](https://www.lokeshsaini.com/blog/designing-the-thing-that-outlives-you) (2026-09-07): The real test of a design system is not launch day. It is whether the work keeps running after you leave. That is a goal you design toward, not a lucky outcome.
- [Five Dark Modes Later](https://www.lokeshsaini.com/blog/five-dark-modes-later) (2026-08-31): It took five attempts to get dark mode right on my own portfolio. Here is what each failure taught me about base colors, elevation, and why the ground matters more than the surfaces.
- [Constraints Are the Clearest Brief You'll Get](https://www.lokeshsaini.com/blog/constraints-are-the-brief) (2026-08-24): Regulatory requirements and hardware limitations are not obstacles to work around. Read them correctly and they tell you exactly what the product has to do.
- [Practicing for Interviews When Interviews Scare You](https://www.lokeshsaini.com/blog/practicing-for-interviews-when-they-scare-you) (2026-08-17): I am good at the work and still find interviews hard. The answer was not to wait for confidence. It was to build a practice system that made the performance part smaller.
- [When You Can't Make It Faster, Make the Waiting Intentional](https://www.lokeshsaini.com/blog/make-the-waiting-intentional) (2026-08-10): Hardware latency you can't remove is still a design material. The craft move is converting a wait into something that reads as feedback.
- [Hard Shadows Are a Constraint, Not a Style](https://www.lokeshsaini.com/blog/hard-shadows-are-a-constraint) (2026-08-03): Ban blur, gradients, and opacity from a design system and something unexpected happens: the decisions get harder, and the results get more honest.
- [The Same Feature Is Help to One User and Surveillance to Another](https://www.lokeshsaini.com/blog/help-to-one-surveillance-to-another) (2026-07-27): When two user groups share one system, a feature does not carry one meaning. Designing for both requires holding two opposed readings of the same screen at once.
- [Thirty Minutes of Research Before I Touch the Application](https://www.lokeshsaini.com/blog/thirty-minutes-before-the-application) (2026-07-20): Every application is a small research project. Here is what changes when you treat it that way.
- [Prototype the Argument Instead of Winning It](https://www.lokeshsaini.com/blog/prototype-the-argument) (2026-07-13): When a team deadlocks on an interaction model, arguing harder just hardens positions. Build both options and let the evidence end the debate before it becomes a conflict.
- [Reading the Role Before Writing a Word](https://www.lokeshsaini.com/blog/reading-the-role-before-writing) (2026-07-06): A senior product designer role and a design-engineer role may both fit you. They are not the same reader.
- [I Stopped Building the Design System First](https://www.lokeshsaini.com/blog/stopped-building-the-design-system-first) (2026-06-29): The instinct to lay a solid foundation before drawing a single screen is backwards. Building the system alongside the screens is what makes both finish on time.
- [Decision-Shaped Stories](https://www.lokeshsaini.com/blog/decision-shaped-stories) (2026-06-22): Walking a panel through your process is a list. Framing the same work around a decision is a narrative. The difference is where interviewers look for judgment.
- [Complexity Is a Safety Problem](https://www.lokeshsaini.com/blog/complexity-is-a-safety-problem) (2026-06-15): Feature count debates miss the point. When your users are vulnerable, every added setting is a new failure mode, and cutting scope becomes a form of harm reduction.
- [The Workshop That Changes the Project](https://www.lokeshsaini.com/blog/workshop-that-changes-the-project) (2026-04-16): Most workshops produce sticky notes and good vibes. A few produce one insight that reframes everything. The difference is the setup, not the activities.
- [Prototyping in the Wrong Tool on Purpose](https://www.lokeshsaini.com/blog/prototyping-in-the-wrong-tool) (2026-04-16): The right prototyping tool depends on the question you're trying to answer, not the phase you're in. Sometimes paper beats Figma and code beats both.
- [Why Node Graphs Fall Apart at 15 Nodes](https://www.lokeshsaini.com/blog/node-graphs-fall-apart-at-fifteen) (2026-04-16): Node graphs demo beautifully with 5 nodes. At 15 they become unreadable. The problem is topology, not tooling.
- [Designing a Learning System Around How My Brain Actually Works](https://www.lokeshsaini.com/blog/learning-system-for-my-brain) (2026-04-16): I have ADHD. Most learning tools ignore that. So I built one that doesn't.
- [Designing for Split Attention: Two Screens, One Story](https://www.lokeshsaini.com/blog/designing-for-split-attention) (2026-04-16): When your interface lives on two devices, the user can only look at one. Sound, haptics, and invisible latency absorption become your real design tools.
- [I Built an Anti-Sycophancy System for My AI Coding Agent](https://www.lokeshsaini.com/blog/anti-sycophancy-system) (2026-04-16): When your AI assistant agrees with everything you say, including the things you get wrong, you have a compliance problem. Here is how I fixed it with hooks, rules, and adversarial agents.