Telephone: 877-277-7643


Home » Team Building » Resolution is the Primary Goal

Resolution is the Primary Goal by Barry Koplowitz


 Cutting Through Opinions
Diagnosing Facts
Providing Resolution

An Network & Application Performance Analyst (NAPA)™ understands their role has political - financial importance.  Resolution = closure.  Diagnosing Application issues using methodical analysis techniques & bulletproof documentation provides opportunity for disagreements to end.  Resolution means Management can make critical decisions about expenditures & actions effecting jobs & productivity.

When lack of resolution is long-standing, there is disagreement - stress.  Different teams have tried many analysis tools - yet haven't found resolution for application or network.  Management, being pushed from above- is pushing others.  Visibility is high - exposure is great.  No one still believes resolution is possible - yet they're under pressure to find resolution. 

A Network & Application Performance Analysis Team provides - Resolution- Process - Expertise - Leadership.  Resolution is always its primary goal - provided through network & application performance analysis - documentation.

Whenever possible NAPA presents documentation to Shareholders, face-to-face with verbal analysis.  Nevertheless, written clarity and usefulness of documentation are critical.  Those Shareholders & Managers who miss presentation meeting - will only see documentation delivered.  Even as a stand-alone deliverable with no verbal explanations, it must be able to provide resolution.  If documentation is weak - vague - open to interpretation - full of fluff - template driven - it doesn't bring resolution.  If Technical Documentation is bulletproof & incontestable - clear & concise - truthful -containing no fluff - not template driven - documentation will be read & understood.  Such documentation brings resolution and closure.

Phase One:  Resolution - Resolution doesn't mean fixing Application - it means diagnosing the Application problem's root-cause - providing useful documentation of analysis with relevant metrics.  Analysis may show correction is not cost effective or reasonable.  That's OK.  There is now agreement between teams.  Client can make informed choices.  By diagnosing root-cause of Application or Performance problems, NAPA provides resolution - fixed or not.

Phase Two:  Correction of Application Issues - Senior Network & Application Performance Analyst (NAPA) must determine how far down "The Rabbit Hole" Client wants to go.  NAPATeam can tune Applications - design new solutions - but these require additional time & expense.   Client has a goal & budget.  Process shows what's possible - but Client must determine limits.  NAPA Team role is to offer analysis, resolution & alternatives.  If correction is desirable - research of Application Performance Tuning options proceed - changes are made to a safe (Dev or Test) environment - new analysis is performed quantifying change's impact.   Technical Documentation updated.

Phase Three: Deployment of Changes into Production Environment - similar testing & performance analysis processes are applied before going live with changes - Diagnosing differences between dev & production environment is key.  Technical Documentation updated.

For the full article and more information on this topic.  Click Here.

This article was published on Wednesday 09 May, 2007.

Back to main topic: Team-Building
The Application & Network Performance Analysis Team (NAPA)™
The Missing Link in IT Management
Mentoring in IT
What's So Great About Packet-Sniffers?
Testing Enviroments--Cost Justification
The Technical Enterprise Practitioner (TEP)™

Newsletter
Signup for our Newsletter:

Search

Search Text

Troubleshooting Info:
New Articles (1)
Application & NetAnalysis (12)
Case Studies . (5)
NetAnalysis Myth Series (5)
Podcasts (2)
Team Building (7)
RSS News Feed
RSS

Information
Contact Us

Copyright © 1999-2008 Interpath Technologies Corporation