Interviewed by Cornelius Fichtner from The Project Management Podcast, our CEO, Jordan Kyriakidis, explore the root causes of poorly written requirements. And more importantly… How to fix them!

Click here to listen to this interview right now:

Here is what Cornelius writes about the interview:

Tomorrow, when you are back at the office working on your project requirements, your goal will be to correctly and succinctly describe the requirements for that project your company is going to launch. The big difference here is that your descriptions have to be 100% on point. You cannot afford to be vague because requirements that can be misinterpreted is a sure-fire way to doom your project. So what can you do to improve your requirements?

The problem of poorly written, ambiguous, and inconsistent requirements is something that Jordan Kyriakidis has thought about a lot. And his answer to this problem is not only a list of “21 Top Tips for Writing an Exceptionally Clear Requirements Document” but also to use computing power. Yes, there is actually a software that will scan your requirements document and tell you what’s wrong with it. (Learn more about QVscribe.)

But we’re not going to talk about the software much, because that would be pretty boring here on an audio podcast. Instead, Jordan and I look at the root causes of poorly written requirements and then we introduce you to the most important 6 out his 21 tips. In that way you can start using your brain power to write better requirements.

About The PM Podcast: Launched in 2005, The Project Management Podcast is hosted by Cornelius Fichtner, PMP, CSM who helps you with your PMP Training in his “real” job. The podcast wants to bring project management to beginners and experts and has done so by publishing hundreds of interviews with project managers from around the world. They are free on