A 30-60-90 Day Plan maps objectives across three months, balancing structured onboarding, focused strategy, and measurable progress. It features a timeline, progressive goals, and specific outcomes. Challenges include time management and adaptability. Use cases span onboarding and project launches. Examples involve marketing and product launch scenarios.
Structured Timeline: The plan segments tasks and objectives into clearly defined 30-day, 60-day, and 90-day periods, providing a timeline for goal achievement.
Progressive Goals: As time advances, the plan sets progressively more challenging goals, with each period building upon the accomplishments of the previous one.
Goal-Oriented: The primary focus of a 30-60-90 day plan is to achieve specific, measurable outcomes within the designated time frames.
Components of a 30-60-90 Day Plan:
30 Days: This initial period typically includes tasks and objectives aimed at achieving quick wins and establishing a strong foundation for the subsequent phases.
60 Days: The second month often involves more intermediate objectives that require building upon the progress made during the first 30 days.
90 Days: The third and final month generally focuses on long-term goals that are designed to be achieved with the knowledge, experience, and momentum gained in the previous two phases.
Benefits of a 30-60-90 Day Plan (Expanded):
A 30-60-90 day plan offers several notable advantages for individuals and organizations alike:
Structured Goal Setting: The plan provides a structured framework for setting goals and objectives, making it easier for individuals to outline what needs to be achieved within specific time frames. This structured approach enhances clarity and focus.
Progress Monitoring: By breaking down larger goals into smaller, time-bound objectives, the plan allows for regular monitoring of progress. This tracking enables individuals and teams to identify areas where they are excelling and areas that may require additional attention.
Adaptability: While the plan provides a clear roadmap, it also allows for adaptability. In dynamic work environments, priorities may shift, and unforeseen challenges may arise. The plan can be adjusted to accommodate changing circumstances and goals.
Onboarding and Integration: In the context of employee onboarding, a 30-60-90 day plan is an invaluable tool for helping new hires integrate seamlessly into their roles and teams. It provides a structured introduction to the company’s culture, processes, and expectations.
Improved Time Management: Setting specific tasks and objectives for each time frame helps individuals manage their time more effectively. This can lead to increased productivity and a better allocation of resources.
Alignment with Organizational Goals: When used within an organization, these plans can ensure that individual and team objectives are aligned with the broader goals and strategies of the company. This alignment fosters cohesion and a unified sense of purpose.
Motivation and Accountability: A well-structured plan can serve as a source of motivation and accountability. It allows individuals to see their progress and celebrate achievements, which can boost morale and motivation.
Enhanced Communication: The plan can be a valuable communication tool, especially when shared with supervisors or team members. It provides transparency about an individual’s or team’s priorities and what they intend to accomplish in the near future.
Risk Mitigation: By setting clear goals and monitoring progress regularly, a 30-60-90 day plan can help identify potential risks and challenges early on. This proactive approach allows for timely adjustments and mitigations.
Challenges of a 30-60-90 Day Plan (Expanded):
While a 30-60-90 day plan offers numerous benefits, it is not without its challenges:
Time Constraints: One of the primary challenges is the constraint of time. Balancing and accomplishing tasks within the designated 30, 60, or 90-day periods can be demanding. Individuals and teams must carefully prioritize and allocate resources.
Scope Creep: In the pursuit of achieving goals within the specified time frames, there is a risk of scope creep—adding more tasks or expanding the scope beyond what was initially planned. This can lead to overextension and decreased effectiveness.
Adapting to Change: The business environment is often dynamic, with shifting priorities and unforeseen disruptions. Adapting a plan to accommodate changing circumstances while staying on course can be a delicate balancing act.
Pressure to Perform: Individuals working under a 30-60-90 day plan may feel increased pressure to perform and achieve their goals within the designated time frames. This pressure can be motivating for some but stressful for others.
Overemphasis on Short-Term Goals: While the plan helps break down long-term objectives, there is a risk of overemphasizing short-term goals at the expense of longer-term strategic planning. Balance is crucial to ensure that immediate tasks align with broader strategies.
Use Cases for a 30-60-90 Day Plan (Expanded):
Employee Onboarding: New employees can benefit significantly from a well-structured onboarding plan that spans their first 30, 60, and 90 days with the company. This plan helps them acclimate to their roles, build relationships, and understand company culture.
Project Management: Project managers often use a 30-60-90 day plan to outline key milestones and objectives for a project’s early phases. It helps ensure that project tasks are executed in a logical sequence and that critical deadlines are met.
Career Development: Individuals seeking career advancement or transitions can create a personalized 30-60-90 day plan to achieve specific career-related goals. This plan may include acquiring new skills, expanding networks, or pursuing education.
Sales and Marketing: Sales and marketing professionals can use this plan to set short-term targets and objectives, such as increasing sales revenue, expanding customer bases, or launching marketing campaigns.
Examples of a 30-60-90 Day Plan (Expanded):
Marketing Director: A marketing director taking on a new role may create a 30-60-90 day plan to outline strategic marketing initiatives, assess their progress, and adjust strategies as necessary to achieve long-term objectives. In the first 30 days, the focus might be on getting acquainted with the team and reviewing existing marketing campaigns. Over the next 60 days, the plan could include developing new marketing strategies, launching campaigns, and analyzing initial results. In the final 90 days, the director may aim to achieve specific growth targets, refine strategies based on data, and prepare for longer-term marketing initiatives.
Product Launch Manager: When launching a new product, a manager may develop a 30-60-90 day plan to guide the process. In the initial 30 days, the focus might be on conducting market research and defining the product’s value proposition. Over the next 60 days, the plan could involve developing a marketingstrategy, creating promotional materials, and coordinating with sales teams. In the final 90 days, the manager may concentrate on the product launch itself, monitoring customer feedback, and planning post-launch activities to drive adoption and sales.
Key Highlights of the 30-60-90 Day Plan Knowledge Graph:
Strategic Roadmap: Illustrates a structured approach to achieving goals in the first three months of a role or project.
Progressive Growth: Emphasizes gradual development with tasks building over time.
Goal-Centric: Focuses on specific outcomes to ensure aligned efforts.
Structured Phases: Divides tasks into 30, 60, and 90-day periods for efficient execution.
Benefits: Streamlines onboarding, aligns strategy, and enables measurable achievements.
Challenges: Addresses time allocation and adaptability in a dynamic environment.
Versatile Use Cases: Applicable in sales management and project launches.
Practical Examples: Showcases real-world scenarios for marketing and product launches.
Framework
Description
When to Apply
30-60-90 Day Plan
A strategic roadmap outlining key goals, priorities, and actions to be accomplished within the first 30, 60, and 90 days of a new role or project. This plan provides a structured approach for onboarding, goal setting, and performance management, helping individuals or teams align their efforts with organizational objectives and achieve success in the initial stages of a new endeavor.
– When starting a new job or project to set clear goals, establish priorities, and accelerate the learning curve during the initial transition period. – During career transitions such as promotions, role changes, or reassignments to ensure a smooth transition and maximize early impact and effectiveness.
Onboarding Guidance
The 30-60-90 day plan serves as a roadmap for effective onboarding by outlining key activities and milestones to be achieved during the initial phases of integration into a new role or organization. It helps newcomers navigate the organizational landscape, build relationships, and understand expectations, processes, and systems, facilitating a smoother transition and accelerating time-to-productivity.
– When welcoming new hires or team members to provide structured guidance and support during the onboarding process. – During leadership transitions to facilitate a smooth handover of responsibilities and ensure continuity in operations and performance.
Goal Setting
The plan establishes clear goals and objectives for the first 30, 60, and 90 days, aligning individual or team efforts with broader organizational priorities and strategic initiatives. By setting specific, measurable, achievable, relevant, and time-bound (SMART) goals, the plan provides focus and direction, enabling individuals or teams to track progress, prioritize activities, and drive meaningful results from the outset.
– When clarifying expectations and defining objectives for new roles, projects, or initiatives to ensure alignment with organizational goals and priorities. – During performance evaluations to establish performance benchmarks and track progress against predefined goals and milestones.
Priority Identification
The plan identifies key priorities and focus areas to be addressed within the first 30, 60, and 90 days, based on critical business needs, stakeholder expectations, and strategic objectives. By prioritizing activities and tasks, individuals or teams can allocate resources effectively, manage time efficiently, and address the most pressing issues or opportunities that contribute to organizational success and impact.
– When managing time and resources effectively in fast-paced environments with competing demands and priorities. – During project kickoffs or change initiatives to identify and prioritize key activities and deliverables for successful project execution and stakeholder engagement.
Relationship Building
The plan includes strategies for building relationships and establishing rapport with key stakeholders, colleagues, clients, and partners within the first 30, 60, and 90 days. By proactively engaging with stakeholders and fostering positive relationships, individuals or teams can gain support, gather insights, and leverage networks to drive collaboration, influence decision-making, and achieve shared objectives more effectively.
– When integrating into new teams or organizations to build trust, credibility, and collaboration with colleagues and stakeholders. – During client or stakeholder engagements to establish rapport and understanding of client needs and expectations from the outset.
Learning and Development
The plan includes provisions for continuous learning, skill development, and professional growth within the first 30, 60, and 90 days. By identifying learning objectives, training opportunities, and skill-building activities, individuals or teams can enhance their capabilities, adapt to new challenges, and stay abreast of industry trends and best practices, ensuring ongoing personal and professional development.
– When investing in employee development and capability building to empower individuals and teams to meet evolving job requirements and industry demands. – During organizational change or transformation initiatives to equip employees with the necessary skills and competencies to navigate change effectively and drive organizational success.
Progress Tracking
The plan includes mechanisms for tracking progress, monitoring performance, and evaluating outcomes against predefined goals and milestones within the first 30, 60, and 90 days. By regularly assessing progress and identifying areas for improvement, individuals or teams can adjust strategies, reallocate resources, and stay on course to achieve desired results, ensuring accountability and transparency in goal attainment.
– When monitoring performance and evaluating effectiveness of actions and strategies to ensure alignment with predefined objectives and desired outcomes. – During performance reviews or check-in meetings to assess progress and provide feedback on performance against established goals and expectations.
Adaptation and Agility
The plan allows for adaptation and flexibility to respond to changing circumstances, emerging priorities, or unexpected challenges within the first 30, 60, and 90 days. By maintaining agility and resilience, individuals or teams can adjust plans, reprioritize tasks, and pivot strategies as needed to address evolving needs and seize new opportunities, ensuring responsiveness and effectiveness in achieving desired outcomes.
– When operating in dynamic and uncertain environments where priorities and requirements may change rapidly. – During crisis management or change management efforts to navigate disruptions and uncertainties effectively while staying focused on key objectives and goals.
Communication Strategy
The plan outlines a communication strategy for sharing progress updates, achievements, and insights with relevant stakeholders, leadership, and team members within the first 30, 60, and 90 days. By fostering open, transparent communication channels, individuals or teams can build trust, manage expectations, and ensure alignment on goals, priorities, and performance outcomes, enhancing collaboration and accountability across the organization.
– When communicating effectively with stakeholders, colleagues, and team members to provide updates, seek feedback, and align on shared objectives and expectations. – During change initiatives or project implementations to maintain stakeholder engagement and transparency throughout the process.
Cultural Integration
The plan includes strategies for cultural integration and alignment with organizational values, norms, and practices within the first 30, 60, and 90 days. By understanding and embracing the organizational culture, individuals or teams can navigate social dynamics, build trust, and demonstrate cultural fit, fostering a sense of belonging and commitment that enhances performance and collaboration across the organization.
– When integrating into new organizational cultures or cross-functional teams to understand norms, values, and expectations and adapt behaviors accordingly. – During mergers or acquisitions to facilitate cultural integration and alignment between merging entities or teams.
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.
Agile Program Management is a means of managing, planning, and coordinating interrelated work in such a way that value delivery is emphasized for all key stakeholders. Agile Program Management (AgilePgM) is a disciplined yet flexible agile approach to managing transformational change within an organization.
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.
Agile leadership is the embodiment of agile manifesto principles by a manager or management team. Agile leadership impacts two important levels of a business. The structural level defines the roles, responsibilities, and key performance indicators. The behavioral level describes the actions leaders exhibit to others based on agile principles.
The andon system alerts managerial, maintenance, or other staff of a production process problem. The alert itself can be activated manually with a button or pull cord, but it can also be activated automatically by production equipment. Most Andon boards utilize three colored lights similar to a traffic signal: green (no errors), yellow or amber (problem identified, or quality check needed), and red (production stopped due to unidentified issue).
Bimodal Portfolio Management (BimodalPfM) helps an organization manage both agile and traditional portfolios concurrently. Bimodal Portfolio Management – sometimes referred to as bimodal development – was coined by research and advisory company Gartner. The firm argued that many agile organizations still needed to run some aspects of their operations using traditional delivery models.
Business innovation is about creating new opportunities for an organization to reinvent its core offerings, revenue streams, and enhance the value proposition for existing or new customers, thus renewing its whole business model. Business innovation springs by understanding the structure of the market, thus adapting or anticipating those changes.
Business model innovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.
A consumer brand company like Procter & Gamble (P&G) defines “Constructive Disruption” as: a willingness to change, adapt, and create new trends and technologies that will shape our industry for the future. According to P&G, it moves around four pillars: lean innovation, brand building, supply chain, and digitalization & data analytics.
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.
A Gemba Walk is a fundamental component of lean management. It describes the personal observation of work to learn more about it. Gemba is a Japanese word that loosely translates as “the real place”, or in business, “the place where value is created”. The Gemba Walk as a concept was created by Taiichi Ohno, the father of the Toyota Production System of lean manufacturing. Ohno wanted to encourage management executives to leave their offices and see where the real work happened. This, he hoped, would build relationships between employees with vastly different skillsets and build trust.
GIST Planning is a relatively easy and lightweight agile approach to product planning that favors autonomous working. GIST Planning is a lean and agile methodology that was created by former Google product manager Itamar Gilad. GIST Planning seeks to address this situation by creating lightweight plans that are responsive and adaptable to change. GIST Planning also improves team velocity, autonomy, and alignment by reducing the pervasive influence of management. It consists of four blocks: goals, ideas, step-projects, and tasks.
The ICE Scoring Model is an agile methodology that prioritizes features using data according to three components: impact, confidence, and ease of implementation. The ICE Scoring Model was initially created by author and growth expert Sean Ellis to help companies expand. Today, the model is broadly used to prioritize projects, features, initiatives, and rollouts. It is ideally suited for early-stage product development where there is a continuous flow of ideas and momentum must be maintained.
An innovation funnel is a tool or process ensuring only the best ideas are executed. In a metaphorical sense, the funnel screens innovative ideas for viability so that only the best products, processes, or business models are launched to the market. An innovation funnel provides a framework for the screening and testing of innovative ideas for viability.
According to how well defined is the problem and how well defined the domain, we have four main types of innovations: basic research (problem and domain or not well defined); breakthrough innovation (domain is not well defined, the problem is well defined); sustaining innovation (both problem and domain are well defined); and disruptive innovation (domain is well defined, the problem is not well defined).
The innovation loop is a methodology/framework derived from the Bell Labs, which produced innovation at scale throughout the 20th century. They learned how to leverage a hybrid innovation management model based on science, invention, engineering, and manufacturing at scale. By leveraging individual genius, creativity, and small/large groups.
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.
As pointed out by Eric Ries, a minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort through a cycle of build, measure, learn; that is the foundation of the lean startup methodology.
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.
Jidoka was first used in 1896 by Sakichi Toyoda, who invented a textile loom that would stop automatically when it encountered a defective thread. Jidoka is a Japanese term used in lean manufacturing. The term describes a scenario where machines cease operating without human intervention when a problem or defect is discovered.
The PDCA (Plan-Do-Check-Act) cycle was first proposed by American physicist and engineer Walter A. Shewhart in the 1920s. The PDCA cycle is a continuous process and product improvement method and an essential component of the lean manufacturing philosophy.
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.
Retrospective analyses are held after a project to determine what worked well and what did not. They are also conducted at the end of an iteration in Agile project management. Agile practitioners call these meetings retrospectives or retros. They are an effective way to check the pulse of a project team, reflect on the work performed to date, and reach a consensus on how to tackle the next sprint cycle. These are the five stages of a retrospective analysis for effective Agile project management: set the stage, gather the data, generate insights, decide on the next steps, and close the retrospective.
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.
The SMED (single minute exchange of die) method is a lean production framework to reduce waste and increase production efficiency. The SMED method is a framework for reducing the time associated with completing an equipment changeover.
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.
Scrumban is a project management framework that is a hybrid of two popular agile methodologies: Scrum and Kanban. Scrumban is a popular approach to helping businesses focus on the right strategic tasks while simultaneously strengthening their processes.
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.
Six Sigma is a data-driven approach and methodology for eliminating errors or defects in a product, service, or process. Six Sigma was developed by Motorola as a management approach based on quality fundamentals in the early 1980s. A decade later, it was popularized by General Electric who estimated that the methodology saved them $12 billion in the first five years of operation.
Stretch objectives describe any task an agile team plans to complete without expressly committing to do so. Teams incorporate stretch objectives during a Sprint or Program Increment (PI) as part of Scaled Agile. They are used when the agile team is unsure of its capacity to attain an objective. Therefore, stretch objectives are instead outcomes that, while extremely desirable, are not the difference between the success or failure of each sprint.
The Toyota Production System (TPS) is an early form of lean manufacturing created by auto-manufacturer Toyota. Created by the Toyota Motor Corporation in the 1940s and 50s, the Toyota Production System seeks to manufacture vehicles ordered by customers most quickly and efficiently possible.
The Total Quality Management (TQM) framework is a technique based on the premise that employees continuously work on their ability to provide value to customers. Importantly, the word “total” means that all employees are involved in the process – regardless of whether they work in development, production, or fulfillment.
The waterfall model was first described by Herbert D. Benington in 1956 during a presentation about the software used in radar imaging during the Cold War. Since there were no knowledge-based, creative software development strategies at the time, the waterfall method became standard practice. The waterfall model is a linear and sequential project management framework.
Gennaro is the creator of FourWeekMBA, which reached about four million business people, comprising C-level executives, investors, analysts, product managers, and aspiring digital entrepreneurs in 2022 alone | He is also Director of Sales for a high-tech scaleup in the AI Industry | In 2012, Gennaro earned an International MBA with emphasis on Corporate Finance and Business Strategy.
