Integration Considerations
In today's interconnected world, integrating with third-party services and platforms has become an essential part of many businesses' operations. One such platform is www.kippy.cloud, which offers various integration capabilities to streamline data management and enhance user experiences. When considering integration with www.kippy.cloud, there are several key factors to take into account. This article explores some of the important considerations to keep in mind.
Ingress: Push data in, Pull data in, or Both
Integrating with www.kippy.cloud requires careful consideration of how data flows into the platform. Depending on your specific needs, you may have the option to push data into www.kippy.cloud, pull data into it, or both. Determining the appropriate ingress method is crucial for ensuring smooth data transfer and seamless integration between your systems and www.kippy.cloud.
Egress: Push data out, Pull data out, or Both
Similar to ingress, egress involves deciding how data will flow out of www.kippy.cloud. Depending on your requirements, you may need to push data out from www.kippy.cloud to other systems, pull data out from somewhere else, or utilize a combination of both approaches. Understanding your data flow requirements will help you establish an effective egress strategy when integrating with www.kippy.cloud.
Granularity: Data and UI
Integration with www.kippy.cloud also involves considering the level of granularity required. This encompasses two main aspects: data and user interface (UI). You need to determine whether you want to integrate at the data level, which involves seamless exchange of information, or at the UI level, which focuses on creating a unified user experience across systems. Defining the desired granularity will help guide your integration approach and ensure a cohesive user experience.
Job Role: Data-Driven by End Users or Low-Level Coding by Developers
Another important consideration when integrating with www.kippy.cloud is the job roles involved in the process. Depending on the complexity and customization required, the integration may be more user-driven or developer-centric. In some cases, end users can drive the integration through self-service tools with basic training, allowing them to configure and manage integrations. On the other hand, more complex integrations may require low-level coding expertise from developers to ensure seamless connectivity and data synchronization.
Skill-Level: Self-Serve with Basic Training or Needs Skill and Experience
Closely related to job roles is the skill-level required for integrating with www.kippy.cloud. This consideration focuses on the capabilities of the individuals involved in the integration process. Some integrations can be self-serviced by end users with basic training, enabling them to handle configuration and management independently. However, more intricate integrations may demand specialized skills and experience to handle complex configurations, troubleshoot issues, and optimize performance. Assessing the skill-level required will help you determine the necessary resources and expertise for a successful integration.
Complexity: Demonstrated, Existing Pattern, or Unproven
The complexity of integration with www.kippy.cloud is another critical factor to evaluate. Integrations can vary in complexity, ranging from those with demonstrated patterns and established best practices to those that are unproven or experimental. Leveraging existing patterns and proven integration methodologies can help simplify the process and minimize risks. However, if your integration requirements are unique or involve cutting-edge technologies, you may need to explore unproven approaches and invest in research and development. Understanding the complexity involved will allow you to assess the feasibility and potential challenges associated with the integration.
Build and Host: Kippy Team, Client Team, or Both
Finally, it is crucial to consider who will be responsible for building and hosting the integration. When integrating with www.kippy.cloud, you have the option to rely on the expertise of the Kippy Team, who can handle the development and hosting of the integration on their platform. Alternatively, you may choose to allocate the responsibility to your own client team, leveraging their expertise and infrastructure. Another possibility is a combination of both teams collaborating on the integration effort. Assessing the available resources, technical capabilities, and desired level of control will help you determine the most suitable approach for building and hosting the integration.
By carefully considering these factors – ingress, egress, granularity, job role, skill level, complexity, and build/host – when integrating with www.kippy.cloud, you can ensure a successful and efficient integration process. Understanding your requirements, evaluating available options, and making informed decisions will pave the way for seamless connectivity, enhanced data management, and improved user experiences within your organization.
​
​
Integration effort by use case
When integrating with www.kippy.cloud, the complexity and effort required can vary depending on the specific use case and the type of integration. Different integration methods have different levels of complexity, and understanding the effort involved can help guide the integration process. Let's explore some common use cases, their corresponding integration types, and the level of effort associated with each.
1. Use Case: Kippy Function
- Type of Integration: Native
- Integration Effort: Low
Integrating the Kippy Function into your system is relatively straightforward with a native integration. The required effort is minimal, allowing for a smooth and efficient integration experience. There are a pre-defined set of functions with a simple Excel-like syntax e.g.
=cloud.kippy.ratio(‘Product defects’, ‘Items produced’)
​
These are relatively easy for end users to learn and apply. They can also be extended provide more complex behaviour - but care must be taken to not create 'config as code' - that is, it is better for anything with non-simple logic to have tests and follow a software development lifecycle.
2. Use Case: Slack
- Type of Integration: Config
- Integration Effort: Low
Integrating with Slack is user-friendly and requires minimal effort. The instance is created using a Slack profile and the end-user can create Communities i.e. which cross-cutting KPIs related to which Slack channels. The integration process can be easily accomplished, resulting in seamless communication between www.kippy.cloud and Slack.
3. Use Case: Google Sign In
- Type of Integration: Config
- Integration Effort: Moderate
Integrating Google Sign In with www.kippy.cloud involves configuration steps that may require a bit more effort. At the most basic-level, the kippy organisation identifier is inferred from the domain of the Google account. With other Enterprise identity solutions, the integration becomes a bit more complicated e.g. the Microsoft (Active Directory) administrator configuring the instance appropriately to determine the kippy organisation identifier and which users are allowed to login to kippy according to the configuration in the directory. However, with the proper documentation and guidance, you can successfully establish the integration and enable users to sign in seamlessly.
4. Use Case: Wrike
- Type of Integration: Config
- Integration Effort: Moderate to High
Integrating with Wrike, a project management platform, using a configuration-based approach may require a moderate to high level of effort. This integration involves setting up and configuring the necessary components to ensure smooth data synchronization between www.kippy.cloud and Wrike. The kippy system owner will configure the shared OAuth2.0 authentication credentials and secrets in both the kippy and wrike system. This will allow end users to specify which KPIs related to which wrike project elements - and vice versa. This use case is a typical example of how an integration with any modern enterprise system would work e.g. ERP, HRS, Production System, etc. The connectivity is usually straight forward - but as the use cases grow in complexity and number - the set up and maintenance effort usually grows exponentially.
5. Use Case: Kippy Adapters
- Type of Integration: Zero Code
- Integration Effort: Low
Integrating with Kippy Adapters using a zero-code approach is designed to be user-friendly and accessible. With pre-built adapters and a simplified configuration process, the integration effort remains low while allowing for customization and efficient data exchange. The approach is similar to the wrike scenario above. However, the complexity of the use cases is abstracted from the end user with 'push/pull' adapters that can be hosted in kippy or in the enterprise estate - and wrapped with a fuller SDLC (Software Development Lifecycle).
6. Use Case: Zapier
- Type of Integration: Zapier
- Integration Effort: High
Integrating with Zapier provides extensive automation capabilities through their pre-built connectors and workflows. While the setup process is user-friendly, the integration effort can be high due to the complexity of designing and configuring custom workflows and data transformations. This provides a quick way for non-IT folk to integrate with a myriad of technologies and create workflows of business processes. The first 'zap' is relatively easy enough with huge satisfaction when it works for the first time. But the implementations are usually quite brittle, only working in the happy path scenarios, with any exception scenarios requiring significant investigation and mitigations. Also, the 'zaps' aren't always free so may not scale well from a cost perspective.
7. Use Case: Microapps
- Type of Integration: Coding
- Integration Effort: Moderate
Integrating microapps involves coding to customize the integration according to specific requirements. The effort required is moderate, as it entails developing custom code to ensure seamless communication and data exchange between www.kippy.cloud and the microapps. The microapps can use the existing APIs and UI patterns to simplify a journey for a persona, scenario or device. And more often than not, the microapps are usually a (slight) variant of existing apps, or amalgamation of other microapps joined together. All this is relatively easy for even a junior/mid-level developer to pick up.
8. Use Case: JSON APIs
- Type of Integration: Coding
- Integration Effort: High
Integrating with JSON APIs involves coding to establish and manage communication between systems. This integration effort is considered high, as it requires developing custom code for API calls, data transformation, and handling processes. However, this is also the most robust, scalable and extensible way of handling non-simple scenarios, especially for exeception and unhappy path scenarios.
Summary
​
By understanding the type of integration and the level of effort required for each use case, organizations can plan their integration projects effectively. Assessing the integration effort will help allocate resources appropriately and ensure successful integration between www.kippy.cloud and the chosen systems or applications.
​
​
Kippy Integration Approaches
When integrating with www.kippy.cloud, organizations have several integration approaches available to connect their systems and applications seamlessly. Each approach offers unique benefits, involves different responsibilities, and is suited for specific integration scenarios. In this section, we will explore various integration approaches offered by Kippy and delve into what they prove, who performs the integration work, and the scenarios they are best suited for. Understanding these approaches will assist organizations in selecting the most suitable strategy for their integration needs.
​
It is worth noting that the specific technologies mentioned here provide an example implementation for a particular approach. The list of previous and possible technologies for integration is obviously much more extensive.
​
Let's dive into the different Kippy integration approaches and explore their key aspects and advantages.
1. Kippy Web APIs
What does it prove?
Kippy Web APIs offered full programmatic interoperability, allowing seamless integration between www.kippy.cloud and other systems or applications. This approach proves the ability to establish robust and flexible connections through simple and standard-based APIs.
Who does the work?
Integration work utilizing Kippy Web APIs is typically performed by development teams. These teams consume the provided APIs, leveraging their programming skills and expertise to establish the necessary connections and data exchange between www.kippy.cloud and the consuming systems or applications. API developers are usually a slightly different breed to front-end or full-stack developers, so it is important to ensure the appropriate skills are available - with at least the appropriate level of head cover to guide and review.
What does it suit?
Kippy Web APIs are well-suited for scenarios that require system-to-system connectivity. This approach is ideal when organizations need to integrate their existing systems or custom applications with www.kippy.cloud in a programmatic manner. Development teams can utilize the provided APIs to build customized integrations tailored to specific business requirements and workflows. This can be when either side of the contract needs to be modfied to optimise the shared interface. The API can also be wrapped with additional connectivity controls, such as VPN networking and finer-grained authorisation.
2. Kippy Microapps
What does it prove?
Kippy Microapps enabled the creation of personalized user interfaces (UIs) tailored to individual users and their specific journeys. This approach proves the ability to bookmark and present custom UI elements dynamically based on user preferences and contextual information. This shows how the kippy platform is extensible - not only in providing addition behaviour - but also being a host for that.
Who does the work?
The work involved in Kippy Microapps integration can be performed by both the Kippy team and the customer. Customers have the flexibility to develop and host their own microapps using the provided tools and frameworks. Alternatively, they can rely on the expertise of the Kippy team to create and manage the microapps on their behalf.
​
What does it suit?
Kippy Microapps are suitable for scenarios that require personalized widgets, dashboards, reports, and journeys within the www.kippy.cloud ecosystem. This approach allows users to customize their UI experience without reinventing the entire cloud collaborative ecosystem. It empowers organizations to tailor the user interface to specific roles, workflows, and preferences, enhancing productivity and user satisfaction. This is for scenarios where it is simpler than having the internal tech team take ownership of part of the wider solution on internal infrastructure.
​
3. Kippy Functions
What does it prove?
Kippy Functions provided the capability to perform copy and math functions per key performance indicator (KPI). This approach proves the ability to manipulate and calculate data based on predefined formulas and rules.
Who does the work?
The work of integrating Kippy Functions falls within the purview of end users. Users can leverage the simple user interface provided by Kippy to input textual entries and utilize the predefined functions to perform calculations and data transformations. It's really as simple as that! Think, typing in =A1 into cell A2 in Excel.
​
What does it suit?
Kippy Functions are well-suited for scenarios that involve simple user textual entries and require basic data manipulation and calculations based on predefined formulas. This approach allows organizations to avoid data duplication by performing calculations directly within www.kippy.cloud. However, it should be noted that Kippy Functions are not designed for complex formula chaining or conditional logic such as If-Then-Else statements.
4. Spreadsheets
What does it prove?
The Spreadsheets integration approach allowed for the import of existing data, facilitating a quick setup process. This approach proves the ability to bring in data from external sources and incorporate it into www.kippy.cloud.
Who does the work?
The work involved in Spreadsheets integration is typically carried out by system administrators. They are responsible for importing the necessary data and defining the structure and content of the spreadsheets. Users can also contribute by providing actual data for the integration.
What does it suit?
The Spreadsheets integration approach is suitable for scenarios where organizations have existing data in spreadsheets that they want to incorporate into www.kippy.cloud. This approach enables a streamlined setup process by allowing system administrators to import data and define the structure. However, it is important to note that the integration primarily focuses on initial setup and data import. It does not support maintaining and synchronizing data in a dual-running mode with Excel or other spreadsheet applications.
5. Zapier
What does it prove?
Zapier integration allowed users to create no-code workflows that span across various cloud technologies. This approach proves the ability to connect different applications and automate tasks without requiring extensive technical expertise. Zapier is an example of one of many "no-code automation tools".
Who does the work?
The integration work using Zapier is primarily performed by non-technical users. With Zapier's user-friendly interface, individuals without coding skills can easily connect to over 4,000 apps using pre-built workflows called "Zaps."
What does it suit?
Zapier is well-suited for scenarios where non-technical users need to establish integrations between different cloud-based applications. This approach empowers users to automate tasks, synchronize data, and streamline workflows across multiple platforms. However, it's important to note that for non-simple use cases that require more advanced customizations, Zapier's capabilities may be limited and the integration process can become costly and cumbersome.
6. Slack
What does it prove?
Integration with Slack enabled functionalities such as Slack login and communities centered around key performance indicators (KPIs). This approach proves the ability to leverage Slack as a platform for authentication and collaboration on KPIs. This is an example of a deep integration for a simple use case - in this example - sending Slack messages to and from kippy. However, the Communities feature is baked into kippy as an add-on only for users signed in via Slack.
​
Who does the work?
The integration work involves the instance owner registering with Slack. They are responsible for establishing the connection between www.kippy.cloud and Slack, enabling users to log in using their Slack credentials. The collaboration on KPIs within Slack can be performed by teams and individuals who are part of the existing Slack culture. The integrations on the kippy side are as deep as the use case requires - but obviously needs effort from the kippy team to design and implement the feature into the product appropriately.
What does it suit?
The Slack integration approach is well-suited for scenarios where organizations already have an established Slack culture. It allows teams to collaborate on KPIs within Slack, leveraging its communication and collaboration features. Additionally, if an organization does not have an existing Slack culture, www.kippy.cloud offers a built-in alternative for collaborating on KPIs. This approach ensures seamless collaboration and a familiar working environment for teams, enhancing productivity and fostering effective communication.
7. Google Sign In
What does it prove?
The Google Sign In integration provided a native integration with a corporate identity provider, allowing users to authenticate using their Google credentials. This approach proves the ability to seamlessly integrate www.kippy.cloud with an organization's existing authentication infrastructure. Kippy has native authentication and authorisation. This is an example of integration with one external identity provider (Google Sign In), but can be used to understand the approach for other integrations to, such as Micrsoft AD, Okra, Forgerock, etc.
​
Who does the work?
The integration work typically involves coordination between the system administrators or IT team responsible for managing the corporate identity provider and the administrators of www.kippy.cloud. The native integration allows for a mix-in with the existing access administrators' standard operating procedures (SOP).
What does it suit?
The Google Sign In integration approach is well-suited for scenarios where organizations want to leverage their corporate identity provider to give and restrict access. It can also help with the curent JML (Joiner-Mover-Leaver) processes within the organisation. This approach enables users to have a single authentication management experience across the enterprise, ensuring convenience and security. Fine-grained role-based access control (RBAC) authorization is typically managed within the www.kippy.cloud application itself, providing flexibility and control over user permissions and access levels.
8. Kippy Adapters
What does it prove?
Kippy Adapters allowed for the integration of www.kippy.cloud with non-standard enterprise systems by enabling push-and-pull of data. This approach proves the ability to abstract the complexity of integrating with diverse systems and productionize the integration process.
Who does the work?
The integration work for Kippy Adapters is primarily performed by IT teams. They are responsible for developing and maintaining the adapters that facilitate the data exchange between www.kippy.cloud and the non-standard enterprise systems. IT teams abstract the complexity of the integration process, ensuring smooth and reliable communication. Code for existing adapters can be reused and modified to get a kick start.
​
What does it suit?
Kippy Adapters are particularly suited for scenarios where integration needs extend beyond standard enterprise systems. This approach allows organizations to connect with diverse and non-standard systems, enabling seamless data exchange. The pre-post processing involved in the integration is wrapped within a software development life cycle (SDLC) build testing process, ensuring that the integration is robust, reliable, and adheres to best practices. By leveraging Kippy Adapters, organizations can overcome the complexities associated with integrating with non-standard enterprise systems and achieve efficient data synchronization with www.kippy.cloud.
​
More examples including integrations with Microsoft Dynamics 365, JDEdwards and SproutHRIS can be found here.
9. Azure DevOps
What does it prove?
The integration with Azure DevOps example showed how you can allow shared code development and collaboration on esoteric use cases. This approach proves the ability to leverage joint development teams and utilize local technical and domain knowledge for implementing the integration.
​
Who does the work?
The integration work is typically performed by joint development teams comprising both technical and domain experts. These teams collaborate to build and implement the shared code required for the esoteric use cases, leveraging their local technical and domain knowledge. For example, the two teams can share the development and (automated) acceptance criteria testing activity - leveraging technical and domain knowledge in he most efficient way.
What does it suit?
The Azure DevOps integration approach is well-suited for scenarios where organizations have complex and specialized use cases that require custom code development. This approach enables efficient collaboration among development teams, leveraging their combined expertise to implement the integration effectively. By utilizing local technical and domain knowledge, organizations can ensure the integration aligns closely with their specific requirements and business processes. Azure DevOps provides a robust platform for version control, project management, and continuous integration/continuous deployment (CI/CD), facilitating seamless development and deployment of the shared code for esoteric use cases.
10. Wrike
What does it prove?
The integration between Wrike, ERP (Enterprise Resource Planning), and HRIS (Human Resources Information System) allowed for the seamless push and pull of data from these enterprise systems. This integration proves the ability to connect and synchronize data between Wrike. This is a typical approach for integration with most modern enterprise systems for ERPs, HRS, Production, etc.
Who does the work?
The integration work involves self-service by administrators who establish an OAuth2.0 connection between Wrike and the respective enterprise systems. Users then drive the data source per key performance indicator (KPI) based on their specific data needs and requirements. The business users are usually familiar with the nuances of the enterprise systems so can wire up to their KPIs. However, other users may have to rely on that domain knowledge when wiring up things for themselves.
What does it suit?
The integration between Wrike approach is suitable for scenarios where organizations need to integrate and exchange data between Wrike and enterprise systems. Administrators can self-serve by establishing the necessary connections, enabling seamless data exchange. Users can then leverage the data source to drive key performance indicators based on real-time data from the integrated systems. It is important to note that the integration primarily focuses on loose-coupled integration from metric to KPI actuals, making it suitable for scenarios that do not involve complex data transformations. It is also best limiting this for the KPIs of the Enterprise domain experts - rather than trying to up-skill all (white-collar and blue-collar) workers on the nuances of the Enterprise system setups.
11. SharePoint Integration
What does it prove?
The integration with SharePoint enabled data-driven integrations, allowing seamless connectivity and data exchange between SharePoint and other systems. This integration proves the ability to establish OAuth connections and leverage SharePoint as a data source for key performance indicators (KPIs) and for the solution to be hosted within the customer's intranet portal - as a seamless extension of their internal working practices.
Who does the work?
The integration work involves self-service by administrators who set up the OAuth2.0 connection between SharePoint and the target systems. Administrators can configure SharePoint as a data source, and users can then drive the data source per KPI based on their specific requirements. The customer teams then embed their widget into their portals, but using connectivity to kippy (e.g. via generic and custom APIs) to manage the data, business logic and processing.
What does it suit?
SharePoint integration approach is well-suited for scenarios where organizations need to integrate their internal tools and portals with a externalized performance management solution. Administrators can self-serve by establishing the OAuth connection, enabling seamless data exchange between SharePoint and other systems. Users can utilize SharePoint's data to drive key performance indicators, incorporating SharePoint data into their reporting and analytics. Additionally, SharePoint integration can be integrated into portals and standard operating procedures (SOP), providing a centralized and unified platform for accessing and managing data across the organization.
​
Summary of approaches:
​
1. Kippy Web APIs: Provided full programmatic interoperability, allowing development teams to consume simple and standard-based APIs for system-to-system connectivity.
2. Kippy Microapps: Enabled the creation of personalized user interfaces (UIs) tailored to individual users and their specific journeys, offering flexibility for customization and enhancing user experience.
3. Kippy Functions: Allowed for copy and math functions per key performance indicator (KPI), facilitating simple user textual entries and data manipulation based on predefined formulas.
4. Spreadsheets: Supported the import of existing data into www.kippy.cloud, making it convenient for quick setup, but not suitable for maintaining and synchronizing data in a dual-running mode with Excel.
5. Zapier: Enabled the creation of no-code workflows that span across various cloud technologies, allowing non-technical users to connect with a wide range of apps, but limited in customizations for non-simple use cases.
6. Slack: Provided Slack login and communities for collaborating on KPIs, either leveraging an existing Slack culture or utilizing the built-in alternative within www.kippy.cloud.
7. Google Sign In: Offered native integration with a corporate identity provider, enabling single authentication management for the enterprise, while fine-grained RBAC authorization is managed within the application.
8. Kippy Adapters: Allowed for push and pull of data from non-standard enterprise systems, abstracting complexity and ensuring robust integration through pre-post processing and SDLC build testing.
9. Azure DevOps: Facilitated shared code development for esoteric use cases, involving joint development teams and utilizing local technical and domain knowledge for implementation.
10. Wrike Integration: Enabled data exchange and synchronization with Wrike, supporting push and pull of data for key performance indicators, primarily for loose-coupled integration and not complex transformations.
11. SharePoint Integration: Provided data-driven integrations with OAuth connection, allowing self-service configuration for administrators and data-driven access to SharePoint for users, integrating into portals and standard operating procedures.
​
These integration approaches offered organizations the flexibility to connect, collaborate, and leverage data from various systems, enhancing productivity, data analysis, and decision-making with www.kippy.cloud.
​
Summary
​
This article explored the considerations and approaches for integrating with www.kippy.cloud, a versatile cloud platform. We discussed the different methods for data ingress and egress, the granularity of integration at the data and UI levels, job roles and skill levels involved in the integration process, the complexity of integrations, and options for building and hosting. Additionally, we examined specific integration approaches showcased in the available demos, such as Kippy Web APIs, Kippy Microapps, Kippy Functions, Spreadsheets, Zapier, Slack, Google Sign In, Kippy Adapters, Azure DevOps, Wrike-ERP-HRIS integration, and SharePoint integration.
​
Integrating with www.kippy.cloud can provide numerous benefits for organizations, including streamlined operations, improved data utilization, and enhanced collaboration. However, careful consideration must be given to various factors such as data ingress/egress methods, granularity, job roles, skill levels, complexity, and integration approaches. By understanding these considerations and selecting the appropriate integration approach based on the specific use case, organizations can maximize the value derived from integrating with www.kippy.cloud. Whether it's leveraging APIs, microapps, functions, external systems, or popular platforms like Zapier, Slack, and SharePoint, organizations can achieve seamless and efficient integration that aligns with their unique requirements. With the right integration strategy in place, organizations can unlock the full potential of www.kippy.cloud and harness its capabilities to drive growth, productivity, and success in their operations.
​
In addition to the considerations and integration approaches discussed in this article, organizations may benefit from exploring the Kippy Enterprise Accelerator Package. This package offers 20 days of consultancy to assist organizations in getting set up with www.kippy.cloud effectively. The package includes comprehensive support, including solution architecture discussions with the technical IT operations team.
The Kippy Enterprise Accelerator Package provides a valuable opportunity for organizations to receive expert guidance and consultation during the integration process. By engaging with this package, organizations can leverage the expertise of the Kippy Team to ensure a smooth and successful integration experience. The consultancy sessions and solution architecture discussions will help organizations align their integration strategy with their specific business needs and technical requirements.
Whether organizations are embarking on their integration journey or looking to optimize their existing integration setup, the Kippy Enterprise Accelerator Package offers a tailored and collaborative approach to ensure a successful integration with www.kippy.cloud.
To learn more about the Kippy Enterprise Accelerator Package and discuss how it can benefit your organization, reach out to the Kippy Team today. Take the next step towards maximizing the potential of www.kippy.cloud and accelerating your integration journey with the support and expertise of the Kippy Enterprise Accelerator Package.
More information about the Enterprise Accelerator Pacakage available on the pricing page.
More information about the demos for the various approach available on the how to guides.
​
I hope this helps - any questions - please contact us via the Live Chat or at support@kippy.me
​​
Thanks,
Nauman
CEO and Founder
kippy - performance management ... made simple