🆕

Coordination Journey

A Systems Integrator experiences the Coordination [Cobbling Solutions Together] Journey —The process of ensuring cohesive operation among multiple solutions.

Job: Coordinating multiple solutions

Last Instance

Multiple Instances

Ongoing Journeys

Job Steps

These are sub-objectives of the overall job following the 9 universal phases of Jobs to be Done. Each step is further supported by several performance metrics that customers use to measure success. These are what get prioritized in a survey.

Click Step ⬇️to Open Performance Metrics ➡️

Identify System Requirements

1. The ability to define and understand the specific needs and requirements of the system that needs to be integrated. This includes understanding the functionality, compatibility, and performance requirements of the system.

Locate Potential Solutions

The ability to find and gather information about potential solutions that can meet the identified requirements. This includes researching different technologies, vendors, and products.

Assess Solution Compatibility

The ability to evaluate whether the potential solutions are compatible with each other and with the existing system. This includes checking technical specifications, interoperability standards, and vendor support.

Prepare Solution Evaluation Criteria

The ability to establish a set of criteria for evaluating the potential solutions. This includes factors such as cost, compatibility, performance, and ease of integration.

Confirm Shortlisted Solutions

The ability to verify and finalize the shortlist of potential solutions based on the evaluation criteria and compatibility checks.

Select Optimal Solutions

The ability to choose the best solutions from the shortlist for implementation. This is the core execution step where the systems integrator makes the decision on which solutions to implement.

Monitor Solution Implementation

The ability to oversee the implementation of the selected solutions to ensure they are installed correctly and functioning as expected. This includes tracking progress, identifying issues, and ensuring quality control.

Resolve Implementation Issues

The ability to troubleshoot and fix any problems that arise during the implementation of the solutions. This includes technical issues, vendor issues, or compatibility issues.

Modify Solution Configuration

The ability to adjust and fine-tune the configuration of the solutions to optimize their performance and integration. This includes making changes to settings, parameters, or workflows.

Validate Solution Functionality

The ability to confirm that the integrated solutions are functioning correctly and meeting the original requirements. This includes validation and performance assessment.

Conclude Integration Project

The ability to finalize the integration project by documenting the work done, providing training to users, and transitioning the system to ongoing operations. This marks the end of the integration project and the start of the system's operational life.

Review Integration Success

The ability to assess the success of the integration project by comparing the final outcome with the original requirements and expectations. This includes gathering feedback from users and stakeholders, and identifying lessons learned for future projects.

Test Integrated Solutions

The ability to conduct thorough testing of the integrated solutions to ensure they are functioning correctly and meeting the original requirements.

Contexts

When jobs have too high of a context, insights tend to be less actionable - or at least relevant for certain stakeholders. These contexts provide a means for narrowing the scope of your research in a consistent and structured fashion. Certainly, more contexts exist, and can be addressed with a specific request.

‣

Software Development Company - In this context, the systems integrator could be coordinating multiple software solutions to create a comprehensive system for the client. This could involve integrating different software applications, databases, and hardware.

‣

Telecommunications Company - Here, the systems integrator might be responsible for coordinating multiple telecommunication solutions, such as integrating different communication channels, networks, and systems.

‣

Healthcare Institution - In a healthcare setting, the systems integrator could be coordinating multiple healthcare solutions, such as integrating different healthcare systems, medical devices, and patient data.

‣

Financial Institution - In a financial institution, the systems integrator could be coordinating multiple financial solutions, such as integrating different financial systems, databases, and transaction systems.

‣

Manufacturing Company - In a manufacturing company, the systems integrator could be coordinating multiple manufacturing solutions, such as integrating different manufacturing systems, machinery, and production lines.

‣

Retail Company - In a retail company, the systems integrator could be coordinating multiple retail solutions, such as integrating different retail systems, point of sale systems, and inventory management systems.

‣

Education Institution - In an education institution, the systems integrator could be coordinating multiple education solutions, such as integrating different education systems, learning management systems, and student data.

‣

Government Agency - In a government agency, the systems integrator could be coordinating multiple government solutions, such as integrating different government systems, databases, and public services.

‣

Transportation Company - In a transportation company, the systems integrator could be coordinating multiple transportation solutions, such as integrating different transportation systems, logistics, and tracking systems.

‣

Construction Company - In a construction company, the systems integrator could be coordinating multiple construction solutions, such as integrating different construction systems, machinery, and project management systems.

‣

Energy Company - In an energy company, the systems integrator could be coordinating multiple energy solutions, such as integrating different energy systems, power grids, and energy management systems.

‣

Agriculture Company - In an agriculture company, the systems integrator could be coordinating multiple agriculture solutions, such as integrating different agriculture systems, machinery, and crop management systems.

‣

Media Company - In a media company, the systems integrator could be coordinating multiple media solutions, such as integrating different media systems, broadcasting, and content management systems.

‣

Hospitality Company - In a hospitality company, the systems integrator could be coordinating multiple hospitality solutions, such as integrating different hospitality systems, booking systems, and customer management systems.

‣

Real Estate Company - In a real estate company, the systems integrator could be coordinating multiple real estate solutions, such as integrating different real estate systems, property management systems, and customer databases.

‣

Insurance Company - In an insurance company, the systems integrator could be coordinating multiple insurance solutions, such as integrating different insurance systems, claim management systems, and customer databases.

‣

Non-profit Organization - In a non-profit organization, the systems integrator could be coordinating multiple non-profit solutions, such as integrating different non-profit systems, donor management systems, and volunteer databases.

‣

Research Institution - In a research institution, the systems integrator could be coordinating multiple research solutions, such as integrating different research systems, data analysis tools, and research databases.

‣

Logistics Company - In a logistics company, the systems integrator could be coordinating multiple logistics solutions, such as integrating different logistics systems, supply chain management systems, and tracking systems.

‣

Consulting Firm - In a consulting firm, the systems integrator could be coordinating multiple consulting solutions, such as integrating different consulting systems, project management tools, and client databases.

Situations

While a group of people may be trying to get the same job done, the way the respond to needs-prioritization questions can be different. When we find statistical clusters of needs we need a way to describe why the group is different from another, not simply that that are different based on how they rate needs. Situations (aka Complexity Factors) that end users experience when they execute the job (or last executed the job) could be different, thus resulting in a different prioritization of specific performance metrics. One or or more situations could correlate to a segment, and it is recommend that follow up interviews are done with actual respondents within a segment to help you gain clarity, and verbatims you can use to construct your strategic storyline for the segment.

Situations/Complexities	1	2	3	4	5
Compatibility of different systems	Incompatible				Fully Compatible
Availability of technical documentation	None				Extensive
Quality of solutions to be integrated	Poor				Excellent
Level of customization required	High				None
Availability of skilled personnel	None				Abundant
Budget for the integration project	Limited				Extensive
Time constraints for project completion	Tight				Flexible
Support from solution providers	Non-existent				Excellent
Complexity of the integration process	High				Low
Stability of the solutions to be integrated	Unstable				Stable
Scalability of the integrated system	Not scalable				Highly scalable
Security of the integrated system	Vulnerable				Highly secure
User-friendliness of the integrated system	Not user-friendly				Highly user-friendly
Maintenance requirements of the integrated system	High				Low
Performance of the integrated system	Poor				Excellent
Level of automation in the integration process	Manual				Fully automated
Interoperability of the solutions to be integrated	Non-interoperable				Fully interoperable
Compliance with industry standards	Non-compliant				Fully compliant
Level of testing required	Extensive				Minimal
Level of stakeholder involvement	High				Low

Ideal States

There are times when going deep into a job, job map, and success metrics is just too much of a gamble. Is it the right job to study? Ideal states give us a handful of indicators that can be used in addition to importance, difficulty, and frequency to understand which jobs groups of end users struggle with, and why.

Understand the specific needs and requirements of the system to be integrated - This is crucial to ensure that the integrated system will function as expected and meet the desired outcomes.
Find and gather information about potential solutions - This is important to ensure that the best possible solutions are considered for integration.
Evaluate the compatibility of potential solutions - This is necessary to ensure that the chosen solutions will work together seamlessly and with the existing system.
Establish a set of criteria for evaluating potential solutions - This helps in making informed decisions about which solutions to implement.
Verify and finalize the shortlist of potential solutions - This ensures that only the most suitable solutions are considered for the final selection.
Choose the best solutions for implementation - This is the core decision-making step that determines the success of the integration project.
Oversee the implementation of the selected solutions - This is necessary to ensure that the solutions are installed correctly and are functioning as expected.
Troubleshoot and fix any problems that arise during implementation - This is crucial to ensure that the integrated system functions smoothly and without interruptions.
Adjust and fine-tune the configuration of the solutions - This is important to optimize the performance of the integrated system and ensure seamless integration.
Conduct thorough testing of the integrated solutions - This is necessary to ensure that the integrated system is functioning correctly and meeting the original requirements.
Confirm that the integrated solutions are functioning correctly - This is crucial to ensure that the integrated system is delivering the expected outcomes.
Finalize the integration project - This marks the end of the integration project and the transition to the operational phase.
Document the work done during the integration project - This is important for future reference and for accountability purposes.
Provide training to users of the integrated system - This is necessary to ensure that the users can effectively use the integrated system.
Transition the system to ongoing operations - This marks the start of the system's operational life.
Assess the success of the integration project - This is important to understand whether the project met its original goals and to learn from the experience.
Gather feedback from users and stakeholders - This is crucial for continuous improvement and for understanding the impact of the integrated system.
Identify lessons learned from the integration project - This is important for improving future integration projects.
Ensure the integrated system meets the original requirements and expectations - This is crucial to ensure that the project is successful and delivers value.
Stay agile and responsive to changes and issues during the integration project - This is important to ensure that the project can adapt to unforeseen challenges and changes.

Financial Metrics

The purchase decision-maker has a say in product selection, and costs relative to cash outlays, direct or indirect, are what they think about. These questions can only be answer by the person who makes those decisions. For consumers, many times you can included these in a core functional study. However, beware of business end users who simply use products that are purchased for them. They are not the right audience for these metrics.

Minimize the cost of integrating multiple solutions to ensure seamless operation.
Minimize the cost of training staff to handle the coordination of multiple solutions.
Minimize the cost of troubleshooting when coordinating multiple solutions.
Minimize the cost of downtime caused by the coordination of multiple solutions.
Minimize the cost of software upgrades required for the coordination of multiple solutions.
Minimize the cost of hardware upgrades needed for the integration of multiple solutions.
Minimize the cost of maintenance for the systems being integrated.
Minimize the cost of licensing fees for the software solutions being coordinated.
Minimize the cost of data migration when coordinating multiple solutions.
Minimize the cost of security measures required for the coordination of multiple solutions.
Minimize the cost of compliance with regulations when coordinating multiple solutions.
Minimize the cost of project management in the coordination of multiple solutions.
Minimize the cost of communication between different solution providers.
Minimize the cost of technical support required for the coordination of multiple solutions.
Minimize the cost of system testing after the coordination of multiple solutions.
Minimize the cost of data backup required when coordinating multiple solutions.
Minimize the cost of system monitoring after the coordination of multiple solutions.
Minimize the cost of system optimization required for the coordination of multiple solutions.
Minimize the cost of system documentation required for the coordination of multiple solutions.
Minimize the cost of system recovery in case of failure during the coordination of multiple solutions.

Related Jobs

When a core functional job is getting close to maturity, we have to look beyond steps or metrics and find other jobs the end user is trying to accomplish so we can help them. This provides an opportunity to not only get a job done better, but get more jobs done on a single platform (and potentially better).

Before Coordinating Multiple Solutions

Identifying Project Requirements - Understand the specific needs and objectives of the project to determine what solutions need to be integrated.
Assessing Current Systems - Evaluate the existing systems to identify any potential compatibility issues with the new solutions.
Researching Potential Solutions - Investigate various solutions that could potentially meet the project requirements.
Establishing Budget Constraints - Determine the financial resources available for the project.
Creating a Project Plan - Develop a detailed plan outlining how the solutions will be coordinated and integrated.

During Coordinating Multiple Solutions

Implementing Solutions - Begin the process of integrating the chosen solutions into the existing system.
Monitoring Progress - Regularly check the progress of the project to ensure it is on track.
Troubleshooting Issues - Address any problems or issues that arise during the implementation process.
Communicating with Stakeholders - Keep all relevant parties informed about the project's progress and any significant developments.
Adjusting the Project Plan as Needed - Make any necessary changes to the project plan based on the progress and any issues that have arisen.

After Coordinating Multiple Solutions

Testing the Integrated System - Conduct thorough testing to ensure that all solutions are working together as expected.
Training Users - Teach end users how to use the new system effectively.
Documenting the Project - Create detailed documentation outlining the project, the solutions used, and any important information for future reference.
Reviewing Project Success - Evaluate the success of the project in terms of meeting the initial objectives and requirements.
Providing Ongoing Support - Offer continued support to end users and make any necessary adjustments to the system based on feedback.

Emotional Jobs

Understanding how end users want to feel (or avoid feeling) in the context of getting the job done is important in several ways. First, understanding this helps to think about more abstract things things a user considers when actually performing the job (or access a service/journey). Second, these insights can be critical in messaging to your offer, which is something your marketing team will value.

Desired Emotions:

Feel Organized: As a systems integrator, it is crucial to feel organized when coordinating multiple solutions. This involves managing various tasks, timelines, and resources effectively.
Feel Confident: Confidence is necessary when making decisions about the integration of different systems. This can help ensure that the right choices are made for the benefit of the project.
Feel Patient: Patience is key when dealing with complex systems and potential issues that may arise during the integration process. This can help maintain a calm and steady approach to problem-solving.
Feel Motivated: Motivation can drive the systems integrator to push through challenges and ensure the successful completion of the project.
Feel Focused: Focus is essential when dealing with the intricate details of system integration. This can help ensure that no important aspect is overlooked.

Undesired Emotions:

Avoid Feeling Overwhelmed: A systems integrator should manage their tasks and responsibilities effectively to avoid feeling overwhelmed. This can help maintain productivity and prevent burnout.
Avoid Feeling Doubtful: Doubt can hinder the decision-making process and create uncertainty. It's important to have confidence in the decisions made during the integration process.
Avoid Feeling Frustrated: Frustration can occur when faced with challenges or setbacks. However, it's important to maintain a positive and solution-oriented mindset.
Avoid Feeling Stressed: High levels of stress can negatively impact performance and well-being. It's important to manage stress effectively during the integration process.
Avoid Feeling Disconnected: As a systems integrator, it's important to stay connected with the team and the project. Feeling disconnected can lead to miscommunication and potential issues.

When coordinating multiple solutions…	How important is it that you are able to…			How difficult is it for you to…
	Not important	Neutral	Important	Not difficult	Neutral	Difficult
Feel Organized
Feel Confident
Feel Patient
Feel Motivated
Feel Focused
Avoid Feeling Overwhelmed
Avoid Feeling Doubtful
Avoid Feeling Frustrated
Avoid Feeling Stressed
Avoid Feeling Disconnected

Social Jobs

Ditto emotional jobs

Positive Perceptions

Be Perceived as Organized - As a systems integrator, it's crucial to be seen as organized. This means having a clear plan, knowing what needs to be done, and when. It also involves keeping track of all the different components and ensuring they're working together seamlessly.
Be Perceived as Technically Proficient - A systems integrator needs to understand the technical aspects of the solutions they're coordinating. Being perceived as technically proficient means others trust your knowledge and ability to handle complex systems.
Be Perceived as Communicative - Communication is key in coordinating multiple solutions. This involves clearly explaining plans, progress, and problems to all stakeholders. Being perceived as communicative means others see you as open, transparent, and easy to work with.
Be Perceived as Reliable - As a systems integrator, you need to deliver on your promises. Being perceived as reliable means others trust you to complete tasks on time and to a high standard.
Be Perceived as Proactive - Proactivity involves anticipating problems before they occur and taking steps to prevent them. Being perceived as proactive shows others that you're committed to ensuring the smooth operation of all systems.

Negative Perceptions

Avoid Being Perceived as Disorganized - Disorganization can lead to missed deadlines, overlooked tasks, and general chaos. It's important to avoid being perceived as disorganized.
Avoid Being Perceived as Technically Inept - A lack of technical knowledge can lead to mistakes and inefficiencies. It's crucial to avoid being perceived as technically inept.
Avoid Being Perceived as Uncommunicative - Poor communication can lead to misunderstandings and frustration. It's important to avoid being perceived as uncommunicative.
Avoid Being Perceived as Unreliable - If you're seen as unreliable, others may hesitate to trust you with important tasks. It's crucial to avoid being perceived as unreliable.
Avoid Being Perceived as Reactive - Being reactive means only dealing with problems once they've occurred, rather than anticipating them. It's important to avoid being perceived as reactive.

Survey Format

When coordinating multiple solutions…	How important is it that you are able to…			How difficult is it for you to…
	Not important	Neutral	Important	Not difficult	Neutral	Difficult
Be Organized
Be Technically Proficient
Be Communicative
Be Reliable
Be Proactive
Avoid Being Disorganized
Avoid Being Technically Inept
Avoid Being Uncommunicative
Avoid Being Unreliable
Avoid Being Reactive

How this was made

I used the tools that I’ve shared in my Jobs-to-be-Done Masterclass: Eliminating Jobs-to-be-Done Interviews with Artificial Intelligence ⬅️ to build this entire catalog.

While it did take some time, that’s because there are 16 journeys and the catalogs are comprehensive. You will not find anything like this in the JTBD practitioner world.

Consultants make their money doing things. Innovators automate things. I hope Customer Experience (CX) professionals are able to leverage this work to accelerate their own.

Purpose

Journey Mapping exercises typically end with a visualization of a make believe journey with a smattering of pain points expressed by a smattering of real people.

Have you ever wondered why you constantly have to redo these?

What I’ve developed above may not be absolutely perfect for your situation, but with a few tweaks it will stand the test of time as the backbone of your prioritization of customer needs, and the foundation of your strategic roadmaps far into the future.

We don’t study solutions, we study the jobs your customers are trying to get done as they experience the lifecycle of ownership within your ecosystem.

Simple as that.

Now, go run a survey. I’ll be incorporating some accelerators for that very, very soon.

Contact

Mike Boysen - Managing Director

Practical JTBD, LLC

www.pjtbd.com | http://jobstobedone.substack.com

678-824-2789 | info@pjtbd.com

Copyright

The entire catalog is covered under creative commons….