1. Week 5
1.1. Organizational forces and barriers
1.1.1. Barriers
1.1.1.1. Status quo
1.1.1.2. Data
1.1.1.3. Politics
1.1.1.4. Culture
1.1.1.5. How would I approach these barriers?
1.1.1.5.1. Utilizing my DiSC=I, I would communicate the importance of innovation and how my idea pertains to it.
1.1.2. Organizational forces impacting success
1.1.2.1. Culture of innovation
1.1.2.2. Structure
1.1.2.3. Risk management
1.1.2.4. Communication
2. Week 4
2.1. Evaluation
2.1.1. Framework
2.1.1.1. Prepare the framework for the idea as part of the delegation process for the innovation team
2.1.1.2. Encourage discussions and challenges to the framework. What does everyone have to say about it?
2.1.1.3. Clearly articulate the overall goal of the project
2.1.1.4. Group assesment
2.1.1.4.1. Measurable oucomes
2.1.2. Data from assessments will be aggregated and observed
2.1.2.1. What outcomes achieved?
2.1.2.1.1. A positive response to assessments from both users and team members. These can be gained both qualitatively and quantitatively through assessments.
3. Week 1
3.1. Description
3.1.1. There is insufficient information provided to blind users through their smartphone app, which is designed to help them
3.1.1.1. I have designed a proposal to improve upon the level of information provided to the user. As an employee of the company, I feel an obligation to help the users
3.1.1.1.1. Innovation Gap: The difference between the stated importance of innovation and the actual results in an organization
3.2. Rationale
3.2.1. We have a commitment to help blind users, which is the basis of the app. Improving upon the well being of people, especially those disadvantaged, should be elementary
3.2.1.1. Point-of-service workers must be able to act to as to meet the demands of the culture of those they serve
3.3. Social context
3.3.1. In order to stay relevant in the business of app making, innovation and catering to 21 century needs is imperative.
3.3.1.1. Technology is ever-changing. We must keep up with the times to stay relevant as a business, to cater to the needs of users, and as individuals.
4. Week 6
4.1. Presentation of idea to VP - April 1st 2015
4.2. Assessments given to team members - April 1st 2015
4.3. Assessments given to users - May 1st 2015
4.4. Evaluation of data from assessments and it's indications - May -June 2015
4.5. Implementation of project - June-July 2015
5. Week 2
5.1. Stakeholders
5.1.1. The VP of operations: is necessary to champion a culture and structure that incessantly encourages, celebrates, and grows innovation. She has the final say if the idea is implemented or not.
5.1.1.1. DiSC = I
5.1.1.1.1. My enthusiasm for this idea will foster an ideal exchange to communicate it's importance to the VP
5.1.1.2. VAT = A
5.1.1.2.1. Email is the preferred method of communication. I can present an audio presentation of my ideas
5.1.2. James Bailey: As the creator of the idea, it's my duty to cultivate it and seek the support from furthest up the hierarchical tier as I can
5.1.2.1. DiSC= I
5.1.2.1.1. Being passionate about the idea, I can communicate it's importance to those who can make it happen.
5.1.2.2. VAT = A
5.1.2.2.1. I need to hear something explained to me in order for it to make sense. I need to hear the logic and the reasoning.
5.1.3. Users of the app: As the primary beneficiaries of the increased amount of information, the user satisfaction is the end game
5.1.3.1. DiSC= all
5.1.3.1.1. Users will vary in their personalities, it's important to cater to everyone.
5.1.3.2. VAT= all
5.1.3.2.1. Again, users will vary in the predominant way they process information. It's important not to focus on a sole way information is processed, but in broader ways.
6. Week 3
6.1. Making a case
6.1.1. What is the companies approach to innovation?
6.1.1.1. Would the idea of such a large change in protocol be taken seriously if proposed by a single employee?
6.1.2. Will other be on board?
6.1.2.1. Seeking the approval of fellow employees can strengthen the campaign. Also, will they abide with being more descriptive for users? It could mean more work for them
6.1.2.1.1. Leading a change in culture
6.1.3. Technical capabilities?
6.1.3.1. Can our programmers and our app handle the increase in the amount of data exchanged?
6.1.4. Creating stakeholder value
6.1.4.1. Will the stakeholders see the point? Will they see the value?
6.1.5. Implementation planning
6.1.5.1. Positives and negatives, can I identify these and communicate their importance to the stakeholders?