Creativity and Innovation Management
2.1 Creativity and Innovation Management means nurturing, developing, and implementing new ideas.
Key Creativity Techniques:
Presenting as many ideas as possible in a group without any criticism.-Types: Traditional, Brain Writing (written ideas in silence), Electronic Brainstorming.
Using a structured list of questions to find ideas: Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse.
Starting by thinking how to make a problem worse. Then converting those negative ideas into solutions.
Breaks a problem into its main parameters and systematically searches all possible combinations. Example - While designing a smartphone: independent consideration of size, battery, material, interface.
Thinking from different perspectives using six colored imaginary hats:
- a) White - Information and data
- b) Red - Emotions and intuition
- c) Black - Risks and negativity
- d) Yellow - Benefits and positivity
- e) Green - Creativity and new ideas
- f) Blue - Control of the thought process
White
Facts & Data
Red
Emotions
Black
Caution
Yellow
Benefits
Green
Creativity
Blue
Process
Figure.2.1 Six thinking hats. Courtesy: The McQuaig Group, 2008
New Product Development (NPD) Process
- Idea Generation - Brainstorming, customer feedback, R&D.
- Idea Screening - Feasibility, profitability, alignment with objectives.
- Concept Development and Testing - With target customers
- Business Analysis - Estimation of cost, price, market size.
- Product Development and Prototyping - Creating prototype, user testing.
- Market Testing - Getting feedback by launching in a limited format.
- Commercialization - Full product launch, marketing and distribution.
- Continuous Improvement - Improvements based on customer feedback.
Example: Indian Snacks Brand - A healthy roasted chickpea snack developed through all stages.
Idea Generation: The company suggests various ideas for new snacks (brainstorming), collects feedback from health-conscious customers, and studies competitors like Haldiram, Bikaji.
a. Idea Screening: Healthy Treat Roasted Chana snack idea is evaluated for feasibility (can we do this?), profitability (will it make money?) and alignment with business objectives, especially from the perspective of providing healthy food supply.
b. Concept Development & Testing: In this stage, the snack concept is developed and tested with a group of health-conscious people, to understand if the product is liked.
c. Business Analysis: Team estimates production cost, potential price, and market size, so that revenue and profit can be understood.
d. Product Development & Prototyping: Snack recipe and packaging are modified based on initial customer feedback.
e. Market Testing: Company launches this snack in some selected shops and makes necessary improvements by taking customer feedback.
f. Commercialization: After successful testing, the snack is launched nationwide, and an extensive marketing campaign is run for it.
9. Continuous Improvement: Feedback is continuously taken from customers and the product is improved accordingly.
Figure 2.2 Launch Process of Snack
Change Management
Change Management is a structured process through which individuals, teams or organizations are moved from the existing state to a desired state. It is extremely essential for successful innovation and adaptation.
Earlier State Bank of India was a large public sector bank working in a traditional manner. It was behind private banks in customer service, technological facilities and digital banking. SBI decided to adopt digital technology in its operations. They launched the YONO (You Only Need One) app, which is a digital banking platform. Employees were trained about the new technology, processes were changed, and easy services were created for customers.
Steps in Change Management:
Using PESTEL Analysis:
- a) Political,
- b) Economic,
- c) Social,
- d) Technological,
- e) Environmental,
- f) Legal factors.
Figure.2.3 PESTEL (Need for change)
Figure 2.4 Kotter's 8 Step Change Model
Product Management
Product Management is the process of guiding a product through its entire lifecycle - from conception to launch and beyond. It involves strategic planning, development, marketing and continuous improvement so that the product can meet customer needs and business objectives. The Product Manager (PM) is a bridge coordinating between customers, business stakeholders, engineering and marketing teams, which is essential for product success.
Strategic Steps for Sustainable Product Design
- i) Identify needs: Understand what customers want and what difficulties they face.
- ii) Example: Saree.com met exact needs by surveying customers about fabric quality and design preferences.
- i) Clear Product Vision: Set objectives aligned with business goals and sustainability.
- ii) Example: Tata Motors sets a goal to reduce pollution by producing electric vehicles.
- i) Eco-friendly materials: Choose recyclable or biodegradable materials.
- ii) Example: Khadi India uses natural, handmade cotton & silk, avoiding chemical waste and helping rural artisans.
- i) Agile method: Develop product in small stages and keep improving it.
- ii) Example: Zoho continuously improves software based on user feedback.
- i) Reuse and Recycling: Design in such a way that products can be reused or easily recycled.
- ii) Example: Paper Boat encourages customers to return used pouches for recycling.
- i) Fair Trade Suppliers: Work with suppliers who use ethical and sustainable methods.
- ii) Example: Amul takes milk from local farmers, gives them fair compensation and reduces pollution caused by transportation. This can be supported as follows:
- Benefit of Local Sourcing: Amul sources its milk supply from local farmers only. This provides farmers with an assured market for their milk. Thus they get appropriate and timely compensation for their hard work.
- Fair Compensation: Amul is run on a cooperative model, where the farmers themselves are partners. Thus the profit is not limited only to intermediaries but reaches the farmers directly. Therefore they get proper prices for milk.
- Reduced Transportation and Pollution Control: Sourcing milk at the local level eliminates the need to bring it from far away. This reduces fuel consumption and consequently carbon emissions and pollution caused by transportation.
- i) Eco Certification: Comply with environmental regulations and obtain recognized certifications.
- ii) Example: Maruti Suzuki complies with ISO 14001 standards and meets fuel efficiency criteria.
- i) Transparency: Clearly communicate your sustainability-related efforts to customers.
- ii) Example: Nudge Foundation (Bangalore) uses environmentally friendly packaging and teaches customers the importance of sustainability.
- i) Feedback and Innovation: Take regular feedback from customers and innovate for sustainability.
- ii) Example: ReNew Power, a renewable energy company in India, continuously innovates in solar technology to increase efficiency and reduce costs.
Agile Product Management
Agile Product Management is an iterative and flexible approach for product management. It emphasizes continuous improvement, customer feedback and cross-functional collaboration. Traditional product management follows a fixed and linear process, while the Agile method focuses on flexibility, speed and delivering value incrementally, so that products develop according to the user's real needs.
The Agile method is especially used in software development, startups and technology-centric industries, but its philosophy can be applied to any product development process.
Benefits of Agile Product Management:
- a) Faster Time-to-Market: Small and useful parts of the product are delivered quickly.
- b) Customer-Centric Approach: Continuous feedback ensures product meets real needs.
- c) Greater Flexibility: Plans can change immediately based on new information.
- d) Improved Collaboration: Cross-functional teams work together.
- e) Risk Reduction: Continuous testing identifies problems early.
- f) Higher Product Quality: Regular improvements reduce bugs.
Agile Manifesto (2001)
4 Core Values:
12 Principles (Agile Principles):
- Customer satisfaction through early and continuous delivery of value.
- Welcome changing requirements, even late in development.
- Deliver working solutions frequently (weeks rather than months).
- Business people and developers must work together daily.
- Build projects around motivated individuals.
- Face-to-face conversation is the best form of communication.
- Working product is the primary measure of progress.
- Sustainable development, able to maintain a constant pace.
- Continuous attention to technical excellence and good design.
- Simplicity--the art of maximizing the amount of work not done--is essential.
- Self-organizing teams make the best decisions.
- Regular reflection and adjustment to become more effective.
Key Agile Frameworks:
- a) Scrum Framework: Iterative development using Sprints and Daily Stand-ups.
- b) Kanban Framework: Visual workflow management system.
- c) Lean Agile Framework: Reducing waste to increase customer value.
- d) SAFe Framework (Scaled Agile Framework): Agile method in scalable format for large companies.
Project Management
Project Management is the process of planning, organizing and executing a project to achieve specific goals within a specific schedule and fixed budget. It includes coordination of resources, risk management, and completing work efficiently and effectively.
Importance of Project Management:
Project Management ensures that projects are completed on time, as per objectives and within budget constraints, and remain aligned with business objectives. It helps the organization achieve the following:
- a) Increasing Efficiency: Clear planning, coordination and resource allocation prevents wastage of time and effort.
- b) Keeping Costs and Risks under Control: Risk assessment and preparation reduces the possibility of major mistakes.
- c) Improving Organizational Collaboration: Clear roles and responsibilities increases harmony within the team.
- d) Quality Delivery: Continuous monitoring maintains the quality of the project.
- e) Adapting to Changes: Agile methods allow plan changes based on feedback.
Areas in Project Management (PMBOK):
a) Defining objectives, outputs and tasks
b) Avoiding “Scope Creep”
a) Setting schedule, deadlines and phases
b) Using Gantt Chart, CPM (Critical Path Method)
a) Preparing budget and keeping costs under control
b) Cost estimation and financial monitoring
a) Checking if output is produced according to set standards
b) Using tools like Six Sigma, TQM
a) Identifying potential risks, analyzing them
b) Preparing alternative plans
a) Role allocation, performance improvement
b) Leadership and stakeholder engagement
a) Effective communication plan
b) Using tools like Google, Microsoft etc.
a) Contract supplier management
b) Acquiring materials and services as needed
a) Managing relationships with customers, sponsors and team members
b) Handling expectations and concerns
The 4 ‘P’s in Project Management:
- People: Team, leadership, stakeholders, communication strategy
- Process: Work methodologies implemented (Agile, Waterfall etc.)
- Product: Final product and outcome of the project
- Project: Complete implementation plan - objectives, risks, resources
Project Life Cycle:
Every project goes through the following 5 structural phases:
- 1. Initiation: Defining objectives, feasibility and scope, stakeholder analysis and obtaining consent
- 2. Planning: Detailed planning, preparing schedule and budget, risk assessment and resource allocation
- 3. Execution: Actually carrying out tasks and outputs, managing team and stakeholders
- 4. Monitoring & Controlling:
i) Monitoring progress and making corrections as needed
ii) Risk and quality control - 5. Closure:
i) Finalizing output, obtaining satisfaction
ii) Project evaluation and documentation
Project Management Tools
Project managers use various tools for project planning, scheduling, monitoring and control. This includes PERT, CPM, Gantt Chart and Budgeting techniques.
1. PERT (Program Evaluation and Review Technique)
It is a statistical method used for determining project schedule and estimating time. Useful for complicated projects with uncertain durations. A network diagram is used, where Nodes mean tasks and Arrows mean their dependencies on each other.
Three time estimates are taken:
- Optimistic (O): Earliest possible completion time
- Pessimistic (P): Longest possible time required
- Most Likely (M): Expected actual time required
Useful for identifying Critical Path
Expected Time (ET) = (Optimistic Time + 4 × Most Likely Time + Pessimistic Time) / 6
ET = (4 + 4×5 + 7) / 6 = 31/6 = 5.17 days
ET = (2 + 4×3 + 4) / 6 = 18/6 = 3 days
ET = (5 + 4×6 + 8) / 6 = 37/6 = 6.17 days
ET = (3 + 4×4 + 5) / 6 = 24/6 = 4 days
ET = (4 + 4×5 + 6) / 6 = 30/6 = 5 days
2. CPM (Critical Path Method)
It is a deterministic method, which identifies the series of tasks (Critical Path) that take the longest duration. For each task, Earliest Start/Finish and Latest Start/Finish times are estimated.
Useful for understanding Slack Time (how much time a task can be delayed without delaying the project) Especially useful for projects with fixed times like construction, production
CPM (Critical Path Method): In Critical Path Method, Expected Time (ET) for each task is taken. The project's Critical Path is the sequence taking the longest time. Based on that, the estimated time for project completion is given.
- Task A: 5.17 days (Predecessors: -)
- Task B: 3 days (Predecessors: A)
- Task C: 6.17 days (Predecessors: A)
- Task D: 4 days (Predecessors: B, C)
- Task E: 5 days (Predecessors: D)
Considering the time of each task and its prerequisites (dependencies), the Critical Path is calculated as follows.
1. A → C → D → E = 5.17 + 6.17 + 4 + 5 = 20.34 days
2. A → B → D → E = 5.17 + 3 + 4 + 5 = 17.17 days
Conclusion: Critical Path: A → C → D → E. The project will take 20.34 days to complete, because this path is the Critical Path.
Table 2.1 – PERT vs CPM
| Feature | PERT | CPM |
|---|---|---|
| Project Type | Research, with uncertainty | Familiar, repetitive |
| Time Estimate | Probabilistic (O, M, P) | Fixed (Fixed Time) |
| Main Focus | Time management and uncertainty | Task dependency and efficiency |
| Use | R&D, IT, Innovation | Construction, Production |
3. Gantt Chart
It is a visual tool that shows tasks in a project, their duration, dependencies and deadlines. Uses bars on a timeline to represent task durations. Dependencies between tasks (e.g.: Finish-to-Start, Start-to-Start) are clarified. It is possible to track progress and make appropriate changes.
Advantages:
- Simple and effective medium – Anyone can understand
- Useful for resource planning
- Useful in both Agile and Waterfall methods
Table 2.2 – Gantt Chart Example:
| Task | Start | End | Duration | Dependencies |
|---|---|---|---|---|
| Research | Mar 1 | Mar 10 | 10 days | None |
| Design | Mar 11 | Mar 20 | 10 days | Research |
| Development | Mar 21 | Apr 10 | 20 days | Design |
| Testing | Apr 11 | Apr 20 | 10 days | Development |
| Deployment | Apr 21 | Apr 25 | 5 days | Testing |
Comparison of PERT, CPM and Gantt Chart
Below, PERT, CPM and Gantt Chart are explained with a simple example through a comparison table. Simple Project Example - Suppose, there is a small project: "Creating a Website", this project has the following 4 tasks:
| Task | Task Name | Time Required (Days) | Predecessors |
|---|---|---|---|
| A | Requirements Analysis | 2 | - |
| B | Design | 4 | A |
| C | Development | 5 | B |
| D | Testing | 3 | C |
Comparison Table:
| Component / Technique | PERT | CPM | Gantt Chart |
|---|---|---|---|
| Full Form | Program Evaluation and Review Technique | Critical Path Method | Gantt Chart |
| Objective | To calculate estimated time for tasks | Finding the longest path (Critical Path) | Placing tasks on a timeline |
| Time Type | Estimate (Optimistic, Most Likely, Pessimistic) | Fixed time | Fixed time |
| Task A to D | ET is calculated: A=2, B=(3+4×4+5)/6=4, C=5, D=3 | A→B→C→D = 2+4+5+3 = 14 days (Critical Path) | All tasks are shown on timeline, such as: A: 1-2 B: 3-6 C: 7-11 D: 12-14 |
| When Used | When there is time uncertainty | When time is fixed | To view tasks and progress in visual format |
| Visual Format | Network Diagram (Node Chart) | Network Diagram (Critical Path Chart) | Bar Chart (Timeline-based Bars) |
| Benefit | Accurate time estimation can be done | Time planning and task priority can be determined | All tasks and progress visible at once |
Estimation and Budgeting in Project Management
Proper cost estimation and budget are essential for sustaining a project financially.
Estimation Techniques:
- a) Top-Down Estimation - Based on previous projects or expert opinion
- b) Bottom-Up Estimation - Independent estimate for each task and then combined
- c) Parametric Estimation - Using historical data + mathematical model
- d) Three-Point Estimation - Using Optimistic, Pessimistic, Most Likely
Budgeting Components:
- i) Direct Costs - Wages, materials, equipment, sub-contractors
- ii) Indirect Costs - Electricity, administrative expenses, rent
- iii) Contingency Reserve - Reserve fund for unexpected expenses
Structure of Project Team: A team of experts from various departments in the main organization, external experts also appointed if necessary, team is dissolved after project completion.
Examples: In IT sector companies like L&T, Infosys, TCS, Wipro, this structure is used for project-based business.