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

The gap is widening between what teams spend on observability tools and the value they receive amid surging data volumes and budget pressures, according to The Breaking Point for Observability Leaders, a report from Imply ...

Seamless shopping is a basic demand of today's boundaryless consumer — one with little patience for friction, limited tolerance for disconnected experiences and minimal hesitation in switching brands. Customers expect intuitive, highly personalized experiences and the ability to move effortlessly across physical and digital channels within the same journey. Failure to deliver can cost dearly ...

If your best engineers spend their days sorting tickets and resetting access, you are wasting talent. New global data shows that employees in the IT sector rank among the least motivated across industries. They're under a lot of pressure from many angles. Pressure to upskill and uncertainty around what agentic AI means for job security is creating anxiety. Meanwhile, these roles often function like an on-call job and require many repetitive tasks ...

In a 2026 survey conducted by Liquibase, the research found that 96.5% of organizations reported at least one AI or LLM interaction with their production databases, often through analytics and reporting, training pipelines, internal copilots, and AI generated SQL. Only a small fraction reported no interaction at all. That means the database is no longer a downstream system that AI "might" reach later. AI is already there ...

In many organizations, IT still operates as a reactive service provider. Systems are managed through fragmented tools, teams focus heavily on operational metrics, and business leaders often see IT as a necessary cost center rather than a strategic partner. Even well-run ITIL environments can struggle to bridge the gap between operational excellence and business impact. This is where the concept of ITIL+ comes in ...

UK IT leaders are reaching a critical inflection point in how they manage observability, according to research from LogicMonitor. As infrastructure complexity grows and AI adoption accelerates, fragmented monitoring environments are driving organizations to rethink their operational strategies and consolidate tools ...

For years, many infrastructure teams treated the edge as a deployment variation. It was seen as the same cloud model, only stretched outward: more devices, more gateways, more locations and a little more latency. That assumption is proving costly. The edge is not just another place to run workloads. It is a fundamentally different operating condition ...

AI can't fix broken data. CIOs who modernize revenue data governance unlock predictable growth-those who don't risk millions in failed AI investments. For decades, CIOs kept the lights on. Revenue was someone else's problem, owned by sales, led by the CRO, measured by finance. Those days are behind us ...

Over the past few years, organizations have made enormous strides in enabling remote and hybrid work. But the foundational technologies powering today's digital workplace were never designed for the volume, velocity, and complexity that is coming next. By 2026 and beyond, three forces — 5G, the metaverse, and edge AI — will fundamentally reshape how people connect, collaborate, and access enterprise resources ... The businesses that begin preparing now will gain a competitive head start. Those that wait will find themselves trying to secure environments that have already outgrown their architecture ...

Ask where enterprise AI is making its most decisive impact, and the answer might surprise you: not marketing, not finance, not customer experience. It's IT. Across three years of industry research conducted by Digitate, one constant holds true is that IT is both the testing ground and the proving ground for enterprise AI. Last year, that position only strengthened ...

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

The gap is widening between what teams spend on observability tools and the value they receive amid surging data volumes and budget pressures, according to The Breaking Point for Observability Leaders, a report from Imply ...

Seamless shopping is a basic demand of today's boundaryless consumer — one with little patience for friction, limited tolerance for disconnected experiences and minimal hesitation in switching brands. Customers expect intuitive, highly personalized experiences and the ability to move effortlessly across physical and digital channels within the same journey. Failure to deliver can cost dearly ...

If your best engineers spend their days sorting tickets and resetting access, you are wasting talent. New global data shows that employees in the IT sector rank among the least motivated across industries. They're under a lot of pressure from many angles. Pressure to upskill and uncertainty around what agentic AI means for job security is creating anxiety. Meanwhile, these roles often function like an on-call job and require many repetitive tasks ...

In a 2026 survey conducted by Liquibase, the research found that 96.5% of organizations reported at least one AI or LLM interaction with their production databases, often through analytics and reporting, training pipelines, internal copilots, and AI generated SQL. Only a small fraction reported no interaction at all. That means the database is no longer a downstream system that AI "might" reach later. AI is already there ...

In many organizations, IT still operates as a reactive service provider. Systems are managed through fragmented tools, teams focus heavily on operational metrics, and business leaders often see IT as a necessary cost center rather than a strategic partner. Even well-run ITIL environments can struggle to bridge the gap between operational excellence and business impact. This is where the concept of ITIL+ comes in ...

UK IT leaders are reaching a critical inflection point in how they manage observability, according to research from LogicMonitor. As infrastructure complexity grows and AI adoption accelerates, fragmented monitoring environments are driving organizations to rethink their operational strategies and consolidate tools ...

For years, many infrastructure teams treated the edge as a deployment variation. It was seen as the same cloud model, only stretched outward: more devices, more gateways, more locations and a little more latency. That assumption is proving costly. The edge is not just another place to run workloads. It is a fundamentally different operating condition ...

AI can't fix broken data. CIOs who modernize revenue data governance unlock predictable growth-those who don't risk millions in failed AI investments. For decades, CIOs kept the lights on. Revenue was someone else's problem, owned by sales, led by the CRO, measured by finance. Those days are behind us ...

Over the past few years, organizations have made enormous strides in enabling remote and hybrid work. But the foundational technologies powering today's digital workplace were never designed for the volume, velocity, and complexity that is coming next. By 2026 and beyond, three forces — 5G, the metaverse, and edge AI — will fundamentally reshape how people connect, collaborate, and access enterprise resources ... The businesses that begin preparing now will gain a competitive head start. Those that wait will find themselves trying to secure environments that have already outgrown their architecture ...

Ask where enterprise AI is making its most decisive impact, and the answer might surprise you: not marketing, not finance, not customer experience. It's IT. Across three years of industry research conducted by Digitate, one constant holds true is that IT is both the testing ground and the proving ground for enterprise AI. Last year, that position only strengthened ...