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

People want to be doing more engaging work, yet their day often gets overrun by addressing urgent IT tickets. But thanks to advances in AI "vibe coding," where a user describes what they want in plain English and the AI turns it into working code, IT teams can automate ticketing workflows and offload much of that work. Password resets that used to take 5 minutes per request now get resolved automatically ...

Governments and social platforms face an escalating challenge: hyperrealistic synthetic media now spreads faster than legacy moderation systems can react. From pandemic-related conspiracies to manipulated election content, disinformation has moved beyond "false text" into the realm of convincing audiovisual deception ...

Traditional monitoring often stops at uptime and server health without any integrated insights. Cross-platform observability covers not just infrastructure telemetry but also client-side behavior, distributed service interactions, and the contextual data that connects them. Emerging technologies like OpenTelemetry, eBPF, and AI-driven anomaly detection have made this vision more achievable, but only if organizations ground their observability strategy in well-defined pillars. Here are the five foundational pillars of cross-platform observability that modern engineering teams should focus on for seamless platform performance ...

For all the attention AI receives in corporate slide decks and strategic roadmaps, many businesses are struggling to translate that ambition into something that holds up at scale. At least, that's the picture that emerged from a recent Forrester study commissioned by Tines ...

From smart factories and autonomous vehicles to real-time analytics and intelligent building systems, the demand for instant, local data processing is exploding. To meet these needs, organizations are leaning into edge computing. The promise? Faster performance, reduced latency and less strain on centralized infrastructure. But there's a catch: Not every network is ready to support edge deployments ...

Every digital customer interaction, every cloud deployment, and every AI model depends on the same foundation: the ability to see, understand, and act on data in real time ... Recent data from Splunk confirms that 74% of the business leaders believe observability is essential to monitoring critical business processes, and 66% feel it's key to understanding user journeys. Because while the unknown is inevitable, observability makes it manageable. Let's explore why ...

Organizations that perform regular audits and assessments of AI system performance and compliance are over three times more likely to achieve high GenAI value than organizations that do not, according to a survey by Gartner ...

Kubernetes has become the backbone of cloud infrastructure, but it's also one of its biggest cost drivers. Recent research shows that 98% of senior IT leaders say Kubernetes now drives cloud spend, yet 91% still can't optimize it effectively. After years of adoption, most organizations have moved past discovery. They know container sprawl, idle resources and reactive scaling inflate costs. What they don't know is how to fix it ...

Artificial intelligence is no longer a future investment. It's already embedded in how we work — whether through copilots in productivity apps, real-time transcription tools in meetings, or machine learning models fueling analytics and personalization. But while enterprise adoption accelerates, there's one critical area many leaders have yet to examine: Can your network actually support AI at the speed your users expect? ...

The more technology businesses invest in, the more potential attack surfaces they have that can be exploited. Without the right continuity plans in place, the disruptions caused by these attacks can bring operations to a standstill and cause irreparable damage to an organization. It's essential to take the time now to ensure your business has the right tools, processes, and recovery initiatives in place to weather any type of IT disaster that comes up. Here are some effective strategies you can follow to achieve this ...

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

People want to be doing more engaging work, yet their day often gets overrun by addressing urgent IT tickets. But thanks to advances in AI "vibe coding," where a user describes what they want in plain English and the AI turns it into working code, IT teams can automate ticketing workflows and offload much of that work. Password resets that used to take 5 minutes per request now get resolved automatically ...

Governments and social platforms face an escalating challenge: hyperrealistic synthetic media now spreads faster than legacy moderation systems can react. From pandemic-related conspiracies to manipulated election content, disinformation has moved beyond "false text" into the realm of convincing audiovisual deception ...

Traditional monitoring often stops at uptime and server health without any integrated insights. Cross-platform observability covers not just infrastructure telemetry but also client-side behavior, distributed service interactions, and the contextual data that connects them. Emerging technologies like OpenTelemetry, eBPF, and AI-driven anomaly detection have made this vision more achievable, but only if organizations ground their observability strategy in well-defined pillars. Here are the five foundational pillars of cross-platform observability that modern engineering teams should focus on for seamless platform performance ...

For all the attention AI receives in corporate slide decks and strategic roadmaps, many businesses are struggling to translate that ambition into something that holds up at scale. At least, that's the picture that emerged from a recent Forrester study commissioned by Tines ...

From smart factories and autonomous vehicles to real-time analytics and intelligent building systems, the demand for instant, local data processing is exploding. To meet these needs, organizations are leaning into edge computing. The promise? Faster performance, reduced latency and less strain on centralized infrastructure. But there's a catch: Not every network is ready to support edge deployments ...

Every digital customer interaction, every cloud deployment, and every AI model depends on the same foundation: the ability to see, understand, and act on data in real time ... Recent data from Splunk confirms that 74% of the business leaders believe observability is essential to monitoring critical business processes, and 66% feel it's key to understanding user journeys. Because while the unknown is inevitable, observability makes it manageable. Let's explore why ...

Organizations that perform regular audits and assessments of AI system performance and compliance are over three times more likely to achieve high GenAI value than organizations that do not, according to a survey by Gartner ...

Kubernetes has become the backbone of cloud infrastructure, but it's also one of its biggest cost drivers. Recent research shows that 98% of senior IT leaders say Kubernetes now drives cloud spend, yet 91% still can't optimize it effectively. After years of adoption, most organizations have moved past discovery. They know container sprawl, idle resources and reactive scaling inflate costs. What they don't know is how to fix it ...

Artificial intelligence is no longer a future investment. It's already embedded in how we work — whether through copilots in productivity apps, real-time transcription tools in meetings, or machine learning models fueling analytics and personalization. But while enterprise adoption accelerates, there's one critical area many leaders have yet to examine: Can your network actually support AI at the speed your users expect? ...

The more technology businesses invest in, the more potential attack surfaces they have that can be exploited. Without the right continuity plans in place, the disruptions caused by these attacks can bring operations to a standstill and cause irreparable damage to an organization. It's essential to take the time now to ensure your business has the right tools, processes, and recovery initiatives in place to weather any type of IT disaster that comes up. Here are some effective strategies you can follow to achieve this ...