Vince Reed recounts an experience of being forced to present software he hadn't seen and attributes the problem to poor planning and communication. He advises software creators to provide detailed, per-page design mockups because developers interpret requirements literally. He concludes that as CEO he takes responsibility for such failures.
I had to go up on stage and show the software without seeing it. All this could have been avoided had maybe two things may not put them in such a tight bind to get this done in time, but at the same time they said that they could. Right. So when you're, when you're young and you're ambitious, sometimes these things happen. So I don't know, I mean, there's a lot of things you can do here or there, but I think I chalk it up to like this experience. Now I. I would say if you are a person creating software, make sure that you get someone that can design how you want the site to look each page. I mean, when they click this button, it should look like this because these developers are going to take what you say literally. So had I had a mock up of every page of how I wanted the site to actually function, then I wouldn't have been in that. So all of it's my fault. I'm joking around. But at the end of the day, as a CEO of a company, you got to take responsibility when you mess up.
