Six Simple Rules of Managing IC Design

Here are six simple rules to consider when managing IC design projects:

1. Commit only after doing your homework. Be creative, be aggressive, keep your vision broad and commit only when you have a means to get there.
2. Keep a keen eye out for the unknown. It is always there, waiting to disrupt your plan.
3. Are things progressing as planned, or is a correction to the plan and/or deliverables in order?
4. Verbalized plans, instructions and decisions should never be considered communicating. Write it down to keep it crisp, concise, thorough and communicated.
5. Leave no room for ambiguity or interpretation in your requirements for success. Say what you need.
6. Due diligence on plans and schedules will reinforce predictability for your design project.

If you want to learn more about managing IC design teams check out the PDF download for a "Managing Excellence in Design Team Execution" seminar.

The Basics of Design Delays

Why does a project end up late? In my experience it comes down to the possibilities outlined below. In reality there is evidence of a touch of all of these on just about any project. Some projects weigh in heavier on some than others.

• Uncontrolled scope expansion (feature creep).
• Ineffective task planning detail.
  
• Disconnects between task deliverable and receivable expectations.
• Undefined or under-defined tasks or information requirements.
• Lack of effective risk mitigation strategies.

Any project delay I have seen can be attributed to one or more of these project deficiencies. Do you believe that it is this simple? This is all stuff that can be easily minimized. Why isn't it being done? Not enough time. I here this all the time and it amazes me how frequently this reason is used. There is always time to do it again but there is never time to do it right. Are you ready to take a stand for the right way to do design? I would like to here if you have been successful in doing this and the project results you have achieved by doing so.