7 Key Technology Roadmap Examples for Your Business

Does your company’s technology spending feel more reactive than strategic? Many organizations acquire new tools and systems without a clear, overarching plan, leading to a disjointed tech stack that fails to deliver real value. A technology roadmap is the solution. It’s a strategic document that brings order to the chaos by aligning every IT initiative with your core business objectives. It forces you to answer the critical "why" behind every investment, ensuring your technology serves as a powerful engine for growth. We'll explore what goes into a successful plan and look at several technology roadmap examples to help you find the right structure for your business challenges.

Key Takeaways

Align Every Tech Project with Business Objectives: Treat your roadmap as a strategic guide that justifies every technology investment by linking it to a specific company goal, such as increasing revenue or improving operations.
Prioritize for a Realistic and Impactful Plan: Build an achievable roadmap by systematically evaluating each initiative based on its business value, resource requirements, technical dependencies, and overall complexity.
Treat Your Roadmap as a Dynamic Conversation: Ensure your roadmap's long-term success by engaging stakeholders continuously, establishing a regular review schedule, and maintaining the flexibility to adapt to new information and changing priorities.

What is a Technology Roadmap (And Why Do You Need One)?

Think of a technology roadmap as the GPS for your company’s tech journey. It’s a high-level, visual plan that shows where you are, where you’re going, and how you plan to get there. It’s not a detailed project plan bogged down with minor tasks; instead, it’s a strategic document that outlines your technology initiatives and connects them to your overarching business goals. For any organization looking to make smart, forward-thinking technology decisions, a roadmap is an essential tool for guidance and clarity.

Defining Its Core Purpose

At its heart, a technology roadmap’s purpose is to communicate your organization's technology strategy. It provides a clear, visual summary of the plan, helping teams make informed choices about their tech stack and future projects. This document serves as a single source of truth, outlining the evolution of your technology over time. It answers key questions for everyone involved: What are we building? Why are we building it? And when will it happen? By laying everything out, a roadmap helps you manage dependencies, plan for new capabilities, and ensure your technology infrastructure can support future growth.

Aligning Technology with Business Goals

A roadmap is the bridge between your IT department and your business objectives. It ensures that every technology investment is a strategic one, directly supporting a larger company goal, whether that’s increasing revenue, improving operational efficiency, or enhancing the customer experience. This strategic document guides your technology investments to prevent random acts of tech adoption, where new tools are acquired without a clear purpose. By forcing you to justify each initiative against business outcomes, the roadmap transforms your IT from a cost center into a powerful engine for growth and innovation, ensuring every dollar spent on technology delivers a measurable return.

Communicating Your Vision Clearly

One of the most significant benefits of a technology roadmap is its power to create alignment. A good roadmap quickly and clearly shares the strategic plan with everyone, from executives and investors to product managers and engineers. It translates complex technical plans into an accessible format that helps all stakeholders visualize the organization's direction and future initiatives. This shared understanding fosters buy-in and collaboration across departments, breaking down silos and ensuring everyone is working toward the same long-term vision. When your entire team understands the "why" behind the "what," you create a more focused and motivated workforce.

What Goes Into an Effective Technology Roadmap?

A great technology roadmap isn't just a wish list. It's a carefully constructed plan that balances ambition with reality, acting as the blueprint for your company's technological future. It details not just what you want to build, but why, when, and how you'll handle any bumps along the way. Each component works together to create a clear, actionable guide that keeps your organization moving in the same direction. Let's break down the essential elements that turn a simple document into a powerful strategic tool.

Setting Clear Goals and Objectives

A successful roadmap starts with a clear destination. Before mapping out projects, define what success looks like for your business. Are you aiming to increase operational efficiency or improve customer experience? Your technology goals must directly support these broader business objectives. A roadmap is a strategic document ensuring every IT initiative is a deliberate step toward your desired outcomes. This alignment is critical, transforming technology spending from a cost center into a strategic investment that drives real, measurable growth.

Planning Timelines and Milestones

An idea without a deadline is just a dream, so a solid timeline with clear milestones is non-negotiable. This part of the roadmap breaks down big goals into manageable phases and deliverables. It creates a visual representation of progress, which is essential for keeping teams accountable and stakeholders informed. Using roadmap tools can help you visualize timelines and track progress against key dates. Establishing milestones helps maintain momentum and ensures everyone understands what needs to be accomplished and by when, preventing projects from stalling.

Allocating Resources and Budget

Your roadmap is only as good as the resources you have to execute it. This is where you get practical about what it will take to bring your vision to life. You need to identify the people, technology, and financial investment required for each initiative. By clearly outlining these needs, the roadmap becomes a powerful tool for securing budget approval and allocating resources effectively. Aligning your roadmap with company objectives ensures every dollar spent contributes directly to delivering maximum value. This step makes sure your plan is both ambitious and achievable.

Assessing and Mitigating Risks

Even the best-laid plans face unexpected challenges. A forward-thinking roadmap anticipates potential roadblocks and includes strategies to address them. This involves identifying risks like new market competition, shifts in technology, internal skill gaps, or budget cuts. Once you've identified these risks, you can develop contingency plans to mitigate their impact. This proactive approach helps you guide technology investments more wisely and prepares your organization to adapt to future changes. By planning for uncertainty, you build resilience into your strategy and increase the likelihood of success.

Common Technology Roadmap Examples for Your Business

Technology roadmaps aren't one-size-fits-all. They adapt to fit specific business needs, from developing a new app to overhauling your entire digital strategy. The right type of roadmap provides a clear, visual plan that aligns your teams and resources toward a specific goal. Understanding the different formats helps you choose the one that will best communicate your technology strategy and guide your projects to success. Below are four common examples that businesses use to organize their technology initiatives.

For Product Development

This roadmap focuses on the technology required to build and improve a product. It’s a high-level plan that outlines the technical requirements, architecture changes, and new frameworks needed to support product features. Unlike a feature-based product roadmap, this one is for your engineering and development teams. It helps them understand what’s most important from a technical standpoint, estimate timelines, and allocate the right resources. This ensures the underlying technology is robust enough to support the product’s growth and evolution, preventing technical debt and enabling future innovation.

For IT Infrastructure and Systems

An IT infrastructure roadmap is all about improving your company’s internal technology backbone. This plan details critical projects like upgrading computer systems, integrating different software applications, and strengthening cybersecurity measures. The primary goal is to make your internal IT operations more efficient, reliable, and secure. It helps you move from reactive problem-solving to proactive system improvements, ensuring your team has the tools they need to perform their best. A well-structured IT roadmap is essential for maintaining business continuity and scaling your operations smoothly.

For Innovation and New Tech

This type of roadmap is forward-looking, centered on exploring and adopting emerging technologies. It outlines projects dedicated to researching and testing new tools like Artificial Intelligence (AI), machine learning, or blockchain to see how they could enhance your business operations. The focus isn't on immediate implementation but on experimentation and learning. An innovation roadmap helps you stay ahead of the curve by creating a structured process for vetting new technologies. It ensures you are strategically investing in future capabilities that could provide a significant competitive advantage down the line.

For Digital Transformation

A digital transformation roadmap is a comprehensive plan that aligns technology initiatives with fundamental business objectives. It goes beyond simple IT upgrades to rethink how your company delivers value to customers. This roadmap connects every digital project, from adopting new cloud infrastructure to implementing CRM software, back to your overarching business goals. It ensures that your technology investments lead to meaningful improvements in efficiency, customer experience, and market position. This strategic view is critical for established companies looking to modernize their operations and thrive in a digital-first world.

How Different Industries Structure Their Roadmaps

A technology roadmap isn't a one-size-fits-all document. While the foundational elements are consistent, the priorities and structure will look very different depending on your industry’s unique pressures, goals, and regulatory landscape. Understanding these nuances is key to creating a roadmap that truly drives your business forward. Seeing how others tailor their plans can give you a great starting point for building your own.

Let’s look at how four major sectors approach their technology roadmaps, each with a distinct focus that reflects its core mission.

Manufacturing: Focusing on Operations

In manufacturing, the primary goal is almost always operational efficiency. Technology roadmaps in this sector are built to streamline processes, reduce costs, and get products out the door faster and more reliably. These plans often detail initiatives for upgrading machinery with automation and robotics. They also map out the implementation of IoT solutions for real-time equipment monitoring and predictive maintenance. A strong manufacturing roadmap will also include strategies for enhancing supply chain management to improve visibility and reduce bottlenecks from start to finish.

Healthcare: Prioritizing Compliance and Care

For healthcare organizations, technology roadmaps perform a delicate balancing act between improving patient care and adhering to strict regulations like HIPAA. The focus is on securely managing sensitive information while delivering better health outcomes. Key initiatives often include the integration of electronic health records (EHR) for a unified patient view and the expansion of telemedicine solutions to increase access to care. These roadmaps also prioritize data analytics to identify trends in patient outcomes, ensuring that every technology investment ultimately serves both the patient and the provider while maintaining compliance.

Finance: Emphasizing Security and Regulation

In the financial industry, security and regulatory compliance are non-negotiable. Technology roadmaps are designed to protect sensitive financial data and maintain customer trust. These plans are heavily weighted toward enhancing cybersecurity measures to defend against ever-evolving threats. You’ll often see projects centered on implementing advanced fraud detection systems that use AI and machine learning. A significant portion of the roadmap is also dedicated to ensuring all systems and processes comply with strict financial regulations and industry standards, making risk mitigation a central theme.

Education: Centering on Learning Systems

The education sector builds its technology roadmaps around one central goal: enhancing the learning experience. These plans outline the adoption and integration of digital tools and platforms that support students and educators. A typical roadmap will include the rollout of a new learning management system (LMS) or upgrades to an existing one to make course materials more accessible. It will also detail initiatives for improving online and hybrid learning environments. Many educational roadmaps now incorporate data analytics tools to help track student performance and engagement, providing insights to personalize and improve instruction.

Choosing the Best Format for Your Roadmap

Once you know what goes into your roadmap, the next step is deciding how to present it. The best format isn't about finding the fanciest template; it's about choosing the layout that communicates your message most effectively to your specific audience. A roadmap for your executive board will look very different from one for your engineering team. The goal is to turn your strategic vision into a clear, visual plan that everyone can understand and get behind.

Think of the format as the lens through which your stakeholders view your technology strategy. Some people need to see strict timelines, while others care more about the business goals driving the initiatives. The right format ensures your plan is not just a document but a powerful tool for alignment and communication. It helps answer critical questions before they are even asked, setting expectations and building confidence in your plan. Whether you’re mapping out a major system migration or a new product launch, our advisory services can help you structure a roadmap that delivers clarity and drives results. Below are a few common formats to consider, each with its own strengths for different situations.

Timeline-Based Layouts

If your primary goal is to communicate when initiatives will be completed, a timeline-based layout is your best bet. This format organizes tasks and projects chronologically, often broken down by month or quarter. It’s a straightforward, high-level visual that helps everyone understand the sequence of events, key deadlines, and how long different phases are expected to take. This layout is particularly useful for presenting to external stakeholders or leadership teams who need a clear picture of the project schedule without getting lost in the technical details. It answers the big-picture questions about timing and resource allocation at a glance.

Feature-Based Structures

When the focus is on what you’re delivering, a feature-based structure is ideal. This format groups initiatives by the specific features, products, or capabilities being developed. It’s a favorite among product and development teams because it directly connects the work being done to the tangible outcomes. Instead of focusing on dates, this roadmap prioritizes the delivery of value. You can organize it by release or by product area, giving teams a clear view of their responsibilities. Using roadmap tools with this structure helps teams visualize and track progress against specific deliverables, keeping everyone aligned on the end goal.

Strategic Theme Formats

For roadmaps that need to answer the question of why, a strategic theme format is the most effective. This approach organizes initiatives under broad company objectives, such as "Enhance Customer Security" or "Streamline Internal Operations." By grouping tasks this way, you directly tie every technology project to a larger business goal. This format is perfect for executive audiences because it clearly demonstrates how technology investments are driving the company’s strategic direction. It shifts the conversation from features and deadlines to business value, ensuring every initiative has a clear purpose and supports your organization's long-term vision.

Gantt Charts and Milestone Views

When you need to manage complexity and dependencies, Gantt charts and milestone views offer the most detail. A Gantt chart is a type of bar chart that illustrates a project schedule, showing the start and finish dates of different tasks and how they relate to one another. This format is invaluable for project managers and teams who need to track progress and manage interconnected workstreams. A milestone view is a simpler version that highlights key achievements or decision points rather than every single task. Both formats are powerful tools for guiding development and fostering transparent communication, especially for large, multi-faceted projects.

How to Prioritize Initiatives on Your Roadmap

Once you have a list of potential technology initiatives, the real work begins: deciding what to tackle first. A roadmap is more than a wish list; it’s a strategic plan where the sequence of events is just as important as the events themselves. Prioritization helps you focus your resources on the projects that will make the biggest difference, ensuring you’re not just busy, but productive.

This process is a careful balancing act. You need to weigh the potential rewards of an initiative against its costs, risks, and dependencies. Getting this right means you can deliver consistent value, maintain momentum, and keep your stakeholders aligned. By systematically evaluating each potential project against a clear set of criteria, you can build a roadmap that is both ambitious and achievable. Let’s walk through the four key factors to consider when organizing your priorities.

Assess the Business Impact

Every initiative on your roadmap should have a clear answer to the question: “How does this help the business?” Prioritizing based on business impact ensures your technology investments are directly tied to strategic goals. This isn’t just about adopting the latest tech; it’s about using technology to drive tangible outcomes like increasing revenue, improving operational efficiency, or enhancing customer satisfaction.

To gauge the impact, evaluate how each project aligns with your company’s key objectives. A new CRM system might directly support a goal to improve customer retention, making it a high-priority item. A server upgrade, while necessary, might have a less direct, but still critical, impact on system stability and performance. This is where a Technology Brokerage-as-a-Service (TBaaS)™ approach can help you connect every technology decision back to a specific business outcome.

Evaluate Resource Availability

An ambitious idea is only as good as your ability to execute it. Before committing to an initiative, you need a realistic picture of your available resources. This includes your team’s bandwidth and skills, your budget, and the time you can allocate to the project. Overlooking these constraints is a common reason why roadmaps fail, leading to burnout, budget overruns, and missed deadlines.

Start by conducting an honest audit of your internal capacity. Do you have team members with the right expertise? If not, can you train them or bring in external help? Consider the financial investment required and make sure it aligns with your budget projections. By matching high-priority initiatives with available resources, you can create a practical plan that your team can confidently deliver on schedule.

Map Out Technical Dependencies

In technology, projects rarely exist in a vacuum. Often, one initiative can’t begin until another is completed. For example, you can’t launch a new data analytics platform until the underlying data warehouse is modernized. These connections are called technical dependencies, and mapping them out is crucial for effective sequencing. Ignoring them can create significant bottlenecks and derail your entire timeline.

Visualize your initiatives and draw lines between them to see how they connect. This exercise helps you identify the foundational projects that need to be completed first to clear the way for others. It also brings clarity to your overall strategy, showing how smaller, tactical projects build toward larger, strategic goals. You can find more insights on strategic planning on our company blog.

Analyze Risk and Complexity

Not all initiatives are created equal. Some are straightforward and low-risk, while others involve new, unproven technologies or require significant organizational change. Analyzing the risk and complexity of each project helps you create a balanced roadmap. You can mix high-risk, high-reward innovation projects with more predictable, foundational improvements to manage your overall exposure.

For each initiative, consider potential hurdles. What could go wrong? How complex is the implementation? A project that involves multiple departments and legacy systems is inherently more complex than a simple software update. By identifying these factors upfront, you can make more informed decisions and develop mitigation plans. If you need help assessing the risk of a potential technology investment, our team of experts is here to provide data-driven guidance.

Common Challenges in Roadmap Implementation

Creating a technology roadmap is a huge step forward, but the real work begins with implementation. Even the most thoughtfully designed plan can encounter obstacles. The key is to anticipate these common hurdles so you can address them proactively instead of letting them derail your progress. From getting teams aligned to managing finite resources, navigating the implementation phase requires careful coordination and clear communication. Understanding these potential challenges is the first step toward building a resilient strategy that can adapt and succeed. Let's look at some of the most frequent issues that arise and how you can prepare for them.

Getting Everyone on the Same Page

One of the biggest challenges is ensuring every team and stakeholder is aligned with the roadmap's vision and priorities. When different departments have their own goals, it’s easy for efforts to become fragmented. Your IT team might be focused on system security, while your marketing team is pushing for a new customer data platform. Without a unified direction, you risk creating silos and internal friction. True strategic alignment requires a holistic view that incorporates perspectives from across the organization. This means fostering commitment among key decision-makers and establishing the roadmap as the single source of truth for all technology initiatives, ensuring everyone is pulling in the same direction.

Adapting to Rapid Tech Changes

Technology doesn't stand still, and a roadmap set in stone can quickly become outdated. The challenge isn't just keeping up with new tools but also managing the human side of change. A successful digital transformation is less about the technology itself and more about the people using it. Your team needs the training and support to adapt to new systems and processes. Building a culture of continuous learning and flexibility is essential. Your roadmap should be a living document, open to adjustments as new technologies emerge and business needs evolve. This allows you to pivot when necessary without abandoning your long-term strategic goals.

Working with Limited Resources

Every organization faces constraints, whether it's budget, time, or personnel. A common refrain is that employees are too busy with daily operations to take on new projects. This is a major risk for roadmap implementation. If your plan is too ambitious for your available resources, you set your team up for burnout and failure. It’s crucial to be realistic about what you can achieve. This involves ruthless prioritization and a clear understanding of your team's capacity. A well-structured roadmap doesn't just outline what you’ll do; it also implicitly states what you won’t do, ensuring your team can focus its energy on the initiatives that deliver the most value.

Overcoming Communication Gaps

Even with a perfectly aligned plan, poor communication can stop a roadmap in its tracks. When information isn't shared effectively, misunderstandings arise, deadlines are missed, and teams can end up working on conflicting tasks. To create value for the long term, you need a coherent course of action supported by consistent communication. This means establishing a regular cadence for updates, making the roadmap easily accessible to everyone, and creating clear channels for feedback. When everyone understands the "why" behind the initiatives and sees how their work contributes to the bigger picture, they are more engaged and motivated to help the plan succeed.

Strategies for a Successful Roadmap Rollout

Creating a technology roadmap is a major accomplishment, but the real work begins when you put it into action. A successful rollout isn't just about executing a plan; it's about bringing people along on the journey and adapting as you go. Even the most brilliant roadmap can fail if it isn't implemented with care and communication. The key is to treat the rollout as a continuous process of engagement, review, and adjustment. Many organizations spend months perfecting a roadmap only to see it collect dust because the implementation strategy was an afterthought. To avoid this, you need to think about the rollout from day one.

By focusing on a few core strategies, you can transform your roadmap from a static document into a dynamic guide that drives real business outcomes. This involves getting the right people involved at the right time, building in checkpoints to stay on course, and maintaining the flexibility to pivot when necessary. A well-executed rollout builds momentum, fosters a culture of accountability, and ensures that your technology choices directly support your company's strategic objectives. Let's walk through the practical steps you can take to ensure your technology roadmap leads to meaningful change and a strong return on investment.

Engage Stakeholders Early and Often

The best way to get buy-in for your roadmap is to make stakeholders part of its creation. When you bring key leaders and department heads into the process from the beginning, their insights shape the final plan, and they become its biggest advocates. This isn't just about a single kickoff meeting; it's about creating an ongoing dialogue. Regular updates and feedback sessions ensure everyone feels heard and understands how the technology initiatives connect to their own goals. This collaborative approach builds a foundation of trust and shared ownership, which is essential for overcoming any hurdles during implementation.

Establish a Regular Review Cadence

A roadmap is a living document, not a one-and-done project. To keep it relevant and effective, you need to schedule regular check-ins. Implementing a consistent review cadence, like a quarterly or bi-annual meeting, gives your team a dedicated time to assess progress against milestones, discuss challenges, and make necessary adjustments. These sessions are crucial for ensuring the roadmap continues to align with evolving business goals. A structured review process keeps the plan front and center, maintains momentum, and ensures your technology investments remain on track to deliver value.

Adopt a Flexible Planning Approach

In the world of technology, change is the only constant. Your roadmap needs to be built with flexibility in mind. Being prepared to adapt your plan in response to new market trends, competitor moves, or internal priority shifts is a sign of strength, not a failure of planning. A rigid roadmap quickly becomes obsolete. By building in room for adjustments, you can seize new opportunities and respond to unexpected challenges without derailing your long-term vision. This flexible planning approach ensures your roadmap remains a useful and realistic guide for your organization.

Foster Cross-Departmental Collaboration

Technology initiatives rarely exist in a vacuum. They impact teams across the entire organization, from marketing and sales to finance and operations. Encouraging collaboration between these departments is vital for a smooth rollout. When different teams work together, you break down silos and uncover innovative solutions that a single department might miss. This ensures the roadmap reflects a complete picture of the organization's needs and capabilities. Fostering a collaborative environment not only improves the outcome of your technology projects but also strengthens the entire business.

Your First Steps to Building a Technology Roadmap

Getting started with a technology roadmap doesn't have to be an overwhelming task. Think of it as creating a clear, actionable guide that shows where your company is heading with its technology. This plan helps align your tech initiatives with your broader business goals, ensuring every investment and project pushes you in the right direction. By breaking the process down into a few initial steps, you can build a solid foundation for a roadmap that guides your team, secures stakeholder buy-in, and drives real results. Let's walk through the first three steps to get you on your way.

Start with Planning and Stakeholder Input

Before you map out any timelines or select new software, your first move is to gather information. A technology roadmap is fundamentally a strategic plan that outlines how technology will support your business objectives. To get this right, you need to talk to people across the company. Engaging stakeholders from different departments early on ensures the roadmap addresses real-world needs and aligns with the company's overall vision. These conversations will help you understand pain points, identify opportunities, and build a plan that everyone feels invested in. This collaborative approach is central to our Technology Brokerage-as-a-Service (TBaaS)™ model, where we prioritize understanding your unique business context first.

Select and Customize Your Template

You don’t need to create your roadmap from a blank page. There are many excellent templates and tools available that can give you a running start. Using a pre-built template helps you structure your thoughts and ensures you don’t miss any critical components. Different roadmap tools are designed for various needs, from product development to IT infrastructure planning. Look for a template that feels intuitive for your team and can be easily customized to fit your specific goals. The right tool will not only help you visualize the plan but also make it easier to track progress and share updates with your stakeholders.

Define Your Timeline and Success Metrics

With your goals and stakeholder input in hand, it's time to get specific. Create a clear timeline that includes key milestones, project phases, and important deadlines. This helps everyone understand the sequence of events and what to expect. Just as important is defining what success looks like. Set clear, measurable goals for each initiative on your roadmap. How will you know if a new technology is delivering the expected value? Regularly checking your progress against these metrics allows you to stay on track and make informed adjustments when needed. This ensures your roadmap remains a living, relevant document that truly guides your technology investments.

Frequently Asked Questions

How is a technology roadmap different from a project plan? Think of it this way: a technology roadmap is your strategic guide, while a project plan is your tactical to-do list. The roadmap answers the big questions like "what are we building and why?" focusing on business goals and outcomes over the next one to three years. A project plan, on the other hand, gets into the details of a single initiative from that roadmap, outlining specific tasks, assigning resources, and setting deadlines for the coming weeks or months.

How often should we update our technology roadmap? There isn't a single magic number, but a good rule of thumb is to review it quarterly and perform a more significant refresh annually. The quarterly check-ins are for making minor adjustments based on project progress or small shifts in the market. The annual update is your chance to re-evaluate your larger strategic goals and ensure the roadmap still aligns with where the business is headed. The key is to treat it as a living document, not something you create once and forget.

Who should own the technology roadmap in an organization? While the CTO or CIO typically leads the charge, the roadmap itself is a collaborative effort. Its ownership should be shared among key leaders from technology, product, and business departments. This shared responsibility ensures the plan isn't created in a vacuum and truly reflects the entire organization's needs and priorities. Having a single executive champion is important for driving the process, but the content and commitment must come from a cross-functional team.

What's the biggest mistake companies make when implementing their roadmap? The most common pitfall is poor communication. Many companies spend a great deal of time creating a beautiful roadmap, only to fail at sharing it effectively across the organization. If teams don't understand the "why" behind the plan or see how their work contributes to the bigger picture, they won't be invested in its success. A roadmap's primary job is to create alignment, and that can only happen with consistent, transparent communication from day one.

Can a roadmap still be useful if our business priorities change frequently? Absolutely. In fact, that's when a roadmap is most valuable. A good roadmap isn't a rigid, unchangeable schedule; it's a strategic framework that guides your decisions. When priorities shift, the roadmap gives you the context to evaluate the change, understand its impact on other initiatives, and make a deliberate, informed pivot. It helps you adapt to change thoughtfully instead of reactively, ensuring your technology strategy remains coherent even when the market is unpredictable.