maybe I’m spoiled by my past. I’m used to having a department dedicated to thorough QA of every bit of product I produce BEFORE the client can see it. It was a sometimes annoying process, but ultimately, it increased the level of quality in my product. Not just because I was being double checked, but i started to learn what things QA picked up on, so I worked to make sure that they weren’t reminding me of the same thing.
Now, I don’t have that catch. Product that isn’t ready is going straight to the client because they want to review it. I totally understand the need for product to be reviewed by the client, but it needs to be thoroughly internally reviewed first. I’m not proud of my work when it’s rushed, but if it has to be rushed, I need to correct my mistakes from the rush before showing it to the client. More importantly, clients shouldnt bein-progress production. Its only fair to the development team, and more importantly, the client. It’s like showing the paying audience a movie before it’s gone through any post-production. Sure, it’s watchable, but it makes a bad impression and doesnt allow the audience to appropriately meter the quality of the product and the process.
I’m working up my ideal application development flow, first draft (super duper mega rough draft) below.
I’m just concerned for the lifecycle of this project, the reputation with the client, the overall quality of my product, and above all, mistakes being repeated.
Whatever you do, don't build your coworking community alone.
Join the 3000+ community builders who get my newest posts, lessons, stories, and tips like "How to fund your coworking space" and "Why I hate the title Community Manager"