How to make a Design proposal
A proposed format:The what, why, how, who and when of a proposal
1. Objective: What to do
1.1. A vague proposal: I will build a slimmest coolest and fastest phone on earth
1.2. Better one: I will build a 5mm x 50mm x 100mm phone with a snapdragon 1GHz quad-core processor
1.3. Clear Objective: Clarity on What to do
2. Purpose: why we need to pursue this proposal
2.1. Vague : It will be the cheapest and largest selling phone in the market
2.2. Better: It will be a under 1000/- rupees phone and expected sales of more than 1 million pieces within six months of launch
2.3.Cause: It will help realize the dream of digital India
3. How: how will you do it
3.1. Budget: 100 crore rupees (including a pay of 1 Lakh/person per month for 25 persons for six months = 1.5 crore rupees
3.2.Team of 25 people: Display, Software and enclosure development:25 crore rupees
3.3. Outsource the motherboard design and fabrication : 50 crore rupees
3.4.Testing: 10 crore rupees
3.5.Marketing: 5 crore rupees
3.6.Contingency fund: 10 crore rupees
3.7.Time to market: 180 days from date of project approval
3.8. How: Have a clear design document
4.Who: the project manager and team leader
4.1. Who: the project manager: Minimum 20 years design experience with a minimum 15 years of service left ( Age: less than 45 years)
4.2. Who: the team leader: Minimum 10 years design experience with a minimum 25 years of service left ( Age: less than 35 years)
4.3. Who: the team members: Engineering post graduates with minimum 6 months of design experience with a minimum 35 years of service left ( Age: less than 25 years)
4.4. Who: clearly define the expected team profile
5.When: Milestones with time-line
5.1. Market survey and literature review-15 days
5.2. Design and planning: Project document finalized: 15 days
5.3. Negotiations and Design finalization with YZX: 15 days
5.4. Parallel S/W and H/W development: first prototype: 30 days
5.5. Integrated final design: 30 days
5.6. Testing and modifications: 30 days
5.7. First phase Production: 15 days
5.8. Market launch and feedback: 30 days
5.9. Full scale production on success
5.10. When: Clearly define milestones with time line
6.Management style:The amount of incentive, based on standard broad guidelines of the organisation and the applying conditions are decided and accepted by all team members before the start of project.
6.1.Collective team responsibility: No incentive to anybody if the project fails.The final answer is Yes or No, nothing in between.
6.2.Collective team leaders responsibility: No incentive to any team leaders if the project fails.The final answer is Yes or No, nothing in between.
6.2.1. The team leaders decide the incentives for his/her team members for the pre-decided tasks.
6.2.2. The pre-decided tasks are independent modules and all team and their members need not be working together.
6.3. The project director's responsibility: No incentive to the project director if the project fails.The final answer is Yes or No, nothing in between. The team leaders and team members get theirs as per their delivery of pre-decided tasks.
7. Online task priority management
7.1.The online tool to handle the individual and team task responsibility, priority and delivery schedule.
7.2. The complete project divided into components of work for three months and team and individual responsibility.
7.3. Each individual and team with a maximum of three clear objective responsibility with three months deadline and priority.
7.4. The task priority can be changed or one task modified/added/deleted once in a month.
7.5. Quarterly delivery of tasks, status and reports for projects than run for more than one year.
Disclaimer:All the above mentioned questions may be not answerable for all types of projects but the most important question is WHY you should do it, WHY you should pursue needs to be answered convincing to the team involved for a sense of PURPOSE and belonging.This will make the team self-driven and no carrot and stick policy will be required.
A proposed format:The what, why, how, who and when of a proposal
1. Objective: What to do
1.1. A vague proposal: I will build a slimmest coolest and fastest phone on earth
1.2. Better one: I will build a 5mm x 50mm x 100mm phone with a snapdragon 1GHz quad-core processor
1.3. Clear Objective: Clarity on What to do
2. Purpose: why we need to pursue this proposal
2.1. Vague : It will be the cheapest and largest selling phone in the market
2.2. Better: It will be a under 1000/- rupees phone and expected sales of more than 1 million pieces within six months of launch
2.3.Cause: It will help realize the dream of digital India
3. How: how will you do it
3.1. Budget: 100 crore rupees (including a pay of 1 Lakh/person per month for 25 persons for six months = 1.5 crore rupees
3.2.Team of 25 people: Display, Software and enclosure development:25 crore rupees
3.3. Outsource the motherboard design and fabrication : 50 crore rupees
3.4.Testing: 10 crore rupees
3.5.Marketing: 5 crore rupees
3.6.Contingency fund: 10 crore rupees
3.7.Time to market: 180 days from date of project approval
3.8. How: Have a clear design document
4.Who: the project manager and team leader
4.1. Who: the project manager: Minimum 20 years design experience with a minimum 15 years of service left ( Age: less than 45 years)
4.2. Who: the team leader: Minimum 10 years design experience with a minimum 25 years of service left ( Age: less than 35 years)
4.3. Who: the team members: Engineering post graduates with minimum 6 months of design experience with a minimum 35 years of service left ( Age: less than 25 years)
4.4. Who: clearly define the expected team profile
5.When: Milestones with time-line
5.1. Market survey and literature review-15 days
5.2. Design and planning: Project document finalized: 15 days
5.3. Negotiations and Design finalization with YZX: 15 days
5.4. Parallel S/W and H/W development: first prototype: 30 days
5.5. Integrated final design: 30 days
5.6. Testing and modifications: 30 days
5.7. First phase Production: 15 days
5.8. Market launch and feedback: 30 days
5.9. Full scale production on success
5.10. When: Clearly define milestones with time line
6.Management style:The amount of incentive, based on standard broad guidelines of the organisation and the applying conditions are decided and accepted by all team members before the start of project.
6.1.Collective team responsibility: No incentive to anybody if the project fails.The final answer is Yes or No, nothing in between.
6.2.Collective team leaders responsibility: No incentive to any team leaders if the project fails.The final answer is Yes or No, nothing in between.
6.2.1. The team leaders decide the incentives for his/her team members for the pre-decided tasks.
6.2.2. The pre-decided tasks are independent modules and all team and their members need not be working together.
6.3. The project director's responsibility: No incentive to the project director if the project fails.The final answer is Yes or No, nothing in between. The team leaders and team members get theirs as per their delivery of pre-decided tasks.
7. Online task priority management
7.1.The online tool to handle the individual and team task responsibility, priority and delivery schedule.
7.2. The complete project divided into components of work for three months and team and individual responsibility.
7.3. Each individual and team with a maximum of three clear objective responsibility with three months deadline and priority.
7.4. The task priority can be changed or one task modified/added/deleted once in a month.
7.5. Quarterly delivery of tasks, status and reports for projects than run for more than one year.
Disclaimer:All the above mentioned questions may be not answerable for all types of projects but the most important question is WHY you should do it, WHY you should pursue needs to be answered convincing to the team involved for a sense of PURPOSE and belonging.This will make the team self-driven and no carrot and stick policy will be required.
No comments:
Post a Comment