3 ms·
I went to a meeting with a prototype once. It was a single happy path with stubbed data, coded in the most naïve way possible. It was, after all, a prototype ju
by cassianoleal 7mo ago
I went to a meeting with a prototype once. It was a single happy path with stubbed data, coded in the most naïve way possible. It was, after all, a prototype just to give a feel for what the interactions would be like.
It put enormous pressure on delivery, since leadership had "already seen it working, how hard could it be to make it to production?"
Never again.
- eptcyka 7mo agoI wouldn’t say “Never again”, unless you put in the caveat that you shouldn’t do this again for the same leaders.
- grepfru_it 7mo agoYou still need the slides to communicate risk, cost, delivery estimates etc. a great way to get your own team and move up in the org
- wil421 7mo agoDid the same thing early in my career. Built a quick bootstrap website with like 5 pages and all the data was static. The backend was a year off. It was great for end users but the non-IT managers were dumb. Same issue about seeing something working and expecting the world.
- anonymars 7mo agoIt's funny (tragicomic) to watch the industry learn the same lessons over and over again (such as "'cheap' overseas outsourcing requires unrealistically precise specs otherwise what would take minutes will take days") This one sounds like "...and this is precisely why we started using wireframes"