Freeze Requirement First
Many employees have been to this problem where outcome not relate to what manager or mentor has expected and what actually they wanted employee to do.
A gap between Miscommunication and Requirement Freeze is a huge actually. Miscommunication is what you get something wrong to do, and Requirement freezing problem is what you have already started without knowing everything about to do.
It is not a problem of only in one sector, this relate to everyone who work based on task systems.
Sometimes a task or a requirements are not been discussed fully even you have started looking into and looking for solution. So most of your productive time get wasted in get a not much fair solution for a half requirement, and when you got to know about there is more things needs to be done and what solution you have made is not enough or not going to work as expected.
Title of this article making sense at this point :) .
I felt many times as a designer, requirements should be handy then and only I should start anything. Cause if everything is not in a single bucket then again same problem will occur of rework.
Our mind is very fast in taking actions in which we are a bit smart, right? That’s how we always start looking for a solution first rather than to look at problems completely, if you forget to do so it will must come back to you as “Rework”.
So to avoid this stuffs, always freeze requirements on what you may going to work and then look for solutions. As solutions can be different for different people for different products. Everyone has their own mentality to look at something and understand it.
Let’s take an example of “Movie ticket booking application”. You have requirement of 5 pages word doc, and before you start you just catch up with titles of a documents only. That will only take you to the modules of application instead of a complexity and logical system flow.
Some modules are based on conditions and user’s data, and if you miss those instructions mentioned in requirements, can make you to do rework again and again. So better to ready full document and freeze it gradually in small milestones.
In such case there is consistent change of requirement phase aries. In that point of time you should first ask for finalize requirement from a manager or mentor to start work on it. If requirement is still like a liquid will not take you to promise deliverables. Or it may be the case of company politics 😆 (not everywhere but yes you should be transparent in your case).
Finalization first attitude can help you in your daily life also in many ways to arrange things, to scheduling time, sort out shopping things etc. If you look up for plan a trip that is not only a task to do, with that you have to make sure about how many actual days you will get to enjoy holiday, where can you go in that duration of time. What kind of trip you and your family are interested in anythings needs to be taken as requirements. So before you finalize everything you have to cross check again to not miss anything. If there is something missed, that may waste your money of all bookings and time too. Right ?
I have seen myself miss some important things before and need to work again for the same things. There I learned “Freeze Requirement First”. Will take some time to do it but can save a lot time of rework on it.
And if you have a clear and finalized requirement you do not need to worry about rest of things. You just need to focus on that particular criteria which requires to finish that particular stuff.
Hope this read make sense to you and worth you time too. Please appreciate by claps.
