Overview
The lecture covers professional conduct with customers, organizing IT support for responsiveness and focus, proactive system advocacy, and strategies to improve IT visibility and manage expectations.
Respectful Customer Interaction
- Use “customers” as the preferred term; avoid insulting labels or jokes at their expense.
- Never call customers stupid; focus on solving the problem, not judging the user.
- Teaching is part of IT roles; help users become self-sufficient when possible.
- Be patient with repeated tasks, like showing printer selection multiple times.
- Avoid public complaints; negative remarks can harm careers and trust.
Priority Setting and Quick Requests
- Customers judge priority by perceived task size, which may not match reality.
- Example mindset: “Let me print one page ahead of a 400-page job” reflects perceived smallness.
- Establish clear triage for quick vs complex tasks to align expectations.
Rapid Response vs Deep-Dive Teams
- Create two groups: rapid response for quick fixes and diagnostic for complex issues.
- Example quick task: password reset; consider self-service password reset tools.
- Mutual Interruption Shield: structure teams to protect focused work from disruptions.
- Swap problematic devices for bench diagnosis to maintain user productivity.
System Advocate: Reactive vs Proactive
- Reactive: fix when it breaks; Proactive: anticipate and prevent failures.
- Build a reputation for helpful, forward-looking solutions users value.
- Example: anticipate printer jams due to environment; relocate or replace proactively.
- Investigate systemic vs isolated performance issues before replacing parts.
Software Acquisition and Installation
- Customers may not understand licensing, server components, or interoperability needs.
- Involve IT before purchases to ensure licensing, disk space, and database connectivity.
- If wrong software arrives, installation delays may be blamed on IT despite user error.
- Interview customers and set timelines to manage expectations before work begins.
Automation: Reactive vs Proactive
- Reactive automation: batch-create accounts at day’s end from a list.
- Proactive automation: immediate account creation upon entry via streamlined workflow.
- Aim to automate end-to-end processes for timely service delivery.
Visibility and the Visibility Paradox
- People notice IT when things break; silence can imply IT is unnecessary.
- Communicate ongoing work to demonstrate value beyond incident response.
- High uptime hides effort; make maintenance and upgrades visible to stakeholders.
Status Communication Practices
- Maintain a system status webpage for current, past, and planned changes.
- Announce outages, upgrades, and incidents with clear timing and scope.
- Users may still call during outages; consistently reference the status page.
Engagement with Management and Departments
- Hold regular one-on-ones with each department to gather needs and feedback.
- Attend staff meetings briefly to check on issues and opportunities.
- Educate managers on possibilities and timelines to align expectations.
Physical Visibility and Workspaces
- Front desk should be accessible; technical staff can sit in low-traffic areas.
- Keep office doors open when possible to signal availability and activity.
- Close doors only for sensitive matters to avoid perceptions of absence.
- Provide quiet zones for developers to minimize interruptions and protect focus.
Town Hall Meetings
- Hold periodic all-customer sessions for bi-directional communication.
- Start with feedback collection; log issues like delays and pain points.
- Present a “state of IT”: current status, plans, staff updates, and acknowledgments.
Key Terms & Definitions
- Mutual Interruption Shield: Organizational design where rapid-response staff shield deep-focus staff from interruptions, and vice versa.
- System Advocate: An IT role mindset that prioritizes proactive, preventative actions and visible value communication.
- Visibility Paradox: The better IT performs (fewer outages), the less visible the effort, risking underappreciation.
Action Items / Next Steps
- Standardize respectful language; train staff on customer interaction norms.
- Implement self-service password reset and define rapid vs complex task queues.
- Formalize Mutual Interruption Shield with staffing and escalation paths.
- Introduce pre-purchase IT consultation for software and licensing checks.
- Create intake interviews and publish timelines for significant requests.
- Upgrade automation to support instant account provisioning.
- Launch and maintain a system status webpage with change calendars.
- Schedule recurring department check-ins and brief meeting drop-ins.
- Establish workspace policies: open-door norms and quiet zones.
- Plan quarterly Town Halls to gather feedback and share IT updates.