Identify the problem and break it down: When we look at the problem, it is about decomposing the bigger issue into smaller pieces. This is called chunking down. We can more easily manage the chunks than trying to tackle everything, everywhere at once.

First, we should identify what the root cause of the problem is before we do anything. This is the hardest step, this will take time to interview all the stakeholders (people who have a vested interest in the success of the upcoming project), determine how far-reaching the problem is, and identify any impacted processes or groups. From this, we should create a problem statement and how this will be resolved in broad-brush or high-level terms (like we did, previously in the introduction).

What to start on first: After the true problem has been identified, we need to do some planning. There will be some logical things that will have to occur before other things can be done. This is also where a budget will come into play (what can we afford to do now and what will have to wait until later). For example, if you are rolling out new software and it won't run on your existing computers, you will have to first order computers, receive them, make sure they have the right software one of them, then deliver them and install them. It wouldn't make sense to have labor waiting to install them before they arrive, would it? This is often a negotiation between the IT department and the client or department getting the project.

Assessment Instructions:

Research and find documentation on how businesses have implemented a bring you own device (BYOD) program. Write a two-page project needs analysis to be presented to management.

• summarize the company and what they do in one paragraph.
• summarize the problem in one paragraph.
• Summarize your perspective on this approach, whether you agree or disagree. However, base your perspective on a manager's view of the problem, not based on emotion. Write your position based on facts, not opinions, detail what you would have done better.