Skip to main content

9 Key Performance Considerations for App Rollouts

Bruce Kosbab

For a successful application rollout, it is vital to assess the user experience appropriately and have an understanding of how the new app impacts your already deployed apps and infrastructure. This requires a great deal of preparation across various IT functions, from network to application teams. To put your team on the path to a successful rollout, take the time to consider the following points before the wide-scale launch:

1. LOCATION

Determine the topology. Where will users access the application and where will the app reside (there may be more than one hosting location)? Is the location intended to be on-premise or off-premise? How will the app behave from remote locations or on mobile devices? How will this impact performance?

2. DATA TRAFFIC

Examine the expected regular traffic load and profile. How does this new app rank in terms of bandwidth priority compared to other apps? How will the additional traffic generated by this new application impact existing app performance? What about overall impact on end-user Quality of Experience?

3. BASELINE

Establish a performance and capacity baseline for the existing infrastructure and applications at all locations. What potential problems could arise after deployment? How does the impact compare to your baseline?

4. PIPE CAPACITY

Determine the most likely path the traffic will take between the application and those user locations. Assess available capacity of both your internal and WAN network – is it sufficient to carry the additional load?

5. LATENCY

Define the new app’s sensitivity to latency. Think about the delay incurred to serve remote locations and mobile users. How will this impact your app deployment?

6. POTENTIAL BOTTLENECKS

Examine capacity and traffic considerations. Is the application using cloud services? Do you have the capability and capacity on the hosting site to allow traffic between the on-premise and off-premise application components?

7. MONITORING

Establish the critical nature of the app. Is this app important enough that you need to configure it for monitoring, either temporarily for the initial rollout or longer-term?

8. LIMITED ROLLOUT

Consider deploying the application to a limited number of test users in each site to get some preliminary testing done. Set expectations for how the application should perform and give users adequate time to acclimate and validate the new application as part of their workflow. How are users receiving the new application? What is the user experience like? Are there any issues that need to be resolved immediately?

9. QUALITY OF EXPERIENCE

After crossing all these hurdles, you can consider moving ahead with a full rollout. Continue to measure the user experience for the new and existing apps, and compare this to your pre-deployment baseline to determine early warning signs of potentially user-impacting behavior. How is the new app stacking up? With any luck the new application will prove to be a valuable addition to the company.

Bruce Kosbab is CTO of Fluke Networks.

Hot Topics

The Latest

AI is becoming the operating system of the enterprise. It acts as an invisible coordination layer that understands intent, connects systems, and executes work across complex SaaS environments. Previously, employees had to click through multiple systems — CRM, ERP, support tools, collaboration platforms — to complete a single task. Now, instead of navigating each application manually, they can simply state what they need to accomplish ...

In 2026, the cost of downtime or an outage is no longer just a technical inconvenience; it's a $600 billion wake up call for global businesses. As our digital ecosystems become  more interconnected, each touchpoint introduces new risks and multiplies the consequences when things go wrong. And the data is clear: aggregate downtime costs  for Global 2,000 companies have surged 50% since 2024, reaching a staggering $600 billion ...

Deloitte found that 74% of enterprises expect to deploy agentic AI solutions in the next 24 months. However, the rush to deployment is outpacing foundational work, though. Only 21% of enterprises have fully formed agent governance models in place. The result? AI agents deployed without guidance or governance begin to function as fragmented islands of complexity ...

Cloud spending is no longer viewed as a passthrough IT expense, but as a strategic financial lever that directly impacts innovation capacity, profitability and enterprise resilience, according to the CFO Cloud Cost Optimization Report from Azul ...

As AI moves from generating responses to performing actions, the need for trust increases exponentially. And as organizations enlist AI agents for increasingly sophisticated business processes, trust is going to be the single most important theme for spurring adoption. What can organizations do to build trustworthy AI agents? ...

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

9 Key Performance Considerations for App Rollouts

Bruce Kosbab

For a successful application rollout, it is vital to assess the user experience appropriately and have an understanding of how the new app impacts your already deployed apps and infrastructure. This requires a great deal of preparation across various IT functions, from network to application teams. To put your team on the path to a successful rollout, take the time to consider the following points before the wide-scale launch:

1. LOCATION

Determine the topology. Where will users access the application and where will the app reside (there may be more than one hosting location)? Is the location intended to be on-premise or off-premise? How will the app behave from remote locations or on mobile devices? How will this impact performance?

2. DATA TRAFFIC

Examine the expected regular traffic load and profile. How does this new app rank in terms of bandwidth priority compared to other apps? How will the additional traffic generated by this new application impact existing app performance? What about overall impact on end-user Quality of Experience?

3. BASELINE

Establish a performance and capacity baseline for the existing infrastructure and applications at all locations. What potential problems could arise after deployment? How does the impact compare to your baseline?

4. PIPE CAPACITY

Determine the most likely path the traffic will take between the application and those user locations. Assess available capacity of both your internal and WAN network – is it sufficient to carry the additional load?

5. LATENCY

Define the new app’s sensitivity to latency. Think about the delay incurred to serve remote locations and mobile users. How will this impact your app deployment?

6. POTENTIAL BOTTLENECKS

Examine capacity and traffic considerations. Is the application using cloud services? Do you have the capability and capacity on the hosting site to allow traffic between the on-premise and off-premise application components?

7. MONITORING

Establish the critical nature of the app. Is this app important enough that you need to configure it for monitoring, either temporarily for the initial rollout or longer-term?

8. LIMITED ROLLOUT

Consider deploying the application to a limited number of test users in each site to get some preliminary testing done. Set expectations for how the application should perform and give users adequate time to acclimate and validate the new application as part of their workflow. How are users receiving the new application? What is the user experience like? Are there any issues that need to be resolved immediately?

9. QUALITY OF EXPERIENCE

After crossing all these hurdles, you can consider moving ahead with a full rollout. Continue to measure the user experience for the new and existing apps, and compare this to your pre-deployment baseline to determine early warning signs of potentially user-impacting behavior. How is the new app stacking up? With any luck the new application will prove to be a valuable addition to the company.

Bruce Kosbab is CTO of Fluke Networks.

Hot Topics

The Latest

AI is becoming the operating system of the enterprise. It acts as an invisible coordination layer that understands intent, connects systems, and executes work across complex SaaS environments. Previously, employees had to click through multiple systems — CRM, ERP, support tools, collaboration platforms — to complete a single task. Now, instead of navigating each application manually, they can simply state what they need to accomplish ...

In 2026, the cost of downtime or an outage is no longer just a technical inconvenience; it's a $600 billion wake up call for global businesses. As our digital ecosystems become  more interconnected, each touchpoint introduces new risks and multiplies the consequences when things go wrong. And the data is clear: aggregate downtime costs  for Global 2,000 companies have surged 50% since 2024, reaching a staggering $600 billion ...

Deloitte found that 74% of enterprises expect to deploy agentic AI solutions in the next 24 months. However, the rush to deployment is outpacing foundational work, though. Only 21% of enterprises have fully formed agent governance models in place. The result? AI agents deployed without guidance or governance begin to function as fragmented islands of complexity ...

Cloud spending is no longer viewed as a passthrough IT expense, but as a strategic financial lever that directly impacts innovation capacity, profitability and enterprise resilience, according to the CFO Cloud Cost Optimization Report from Azul ...

As AI moves from generating responses to performing actions, the need for trust increases exponentially. And as organizations enlist AI agents for increasingly sophisticated business processes, trust is going to be the single most important theme for spurring adoption. What can organizations do to build trustworthy AI agents? ...

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...