Stakeholders Clients
Post #3548 · source on Telegram
The Unfinished UI Feedback Loop
Description
A screenshot of a tweet by Rachit Mishra that perfectly captures the frustrating dynamic between a developer and an impatient client. The tweet is a short script: Client: 'Is it ready?' Me: 'No, I still nee..' Client: 'Why is the UI like this?' Me: 'That's what I'm tryi...' Client: 'Damn, this is not what I want, change it.' This interaction is painfully relatable for any developer who has had a non-technical stakeholder review work-in-progress. The humor comes from the client's complete inability to grasp that the product is unfinished, leading them to give feedback on a feature that is still actively being built. It highlights a classic failure in communication and managing client expectations
More like this
More like this in Stakeholders Clients →
Use J and K for navigation
Comments
8Comment deleted
The fastest way to get a client to approve a design is to show them the placeholder UI on the dev server and tell them it's the final version
Our new rule of thumb: every time the client cuts me off mid-sentence, we spin up another micro-frontend. By the next “is it ready?” we’ll have 40 repos, zero cohesive UI, and a textbook case study on Conway’s Law
After 20 years in tech, I've learned that clients have a special quantum superposition ability - they can simultaneously want something 'exactly like the mockup' while also wanting it 'completely different' until you observe the final invoice
The classic client Heisenberg uncertainty principle: you cannot simultaneously have them observe your work-in-progress AND maintain their understanding that it's not finished. The moment they see the UI, the wavefunction of 'reasonable expectations' collapses into 'why doesn't this look like the final mockup I approved three sprints ago?'
Client triggered changeRequest() while the feature flag was off - returned 409 SpecConflict, escalated to a P0 redesign by EOD
Client UI feedback: the only infinite loop that doesn't crash the browser, but sure tanks your sprint velocity
The UI enters a Schrödinger sprint: until release it’s simultaneously “not ready” and “already wrong” - somehow also out of scope per the SOW
Literally the agile Comment deleted