dependency by ajizai


									     Are You Too Dependent on
       Your Technology Staff?

Adapted from a presentation by:

Joe Rutter
Knowledge Manager
Ohio SchoolNet

State Technology Conference, February 3-5. 2002
Why do computer users need
   Technology and computers can be complicated
   Some individuals are more “tech savvy” than
   Some tasks and operations are done infrequently
    and are not well understood
   Security issues (especially Windows XP)
   Other reasons…
     What Sources of Help are
   Self-help
    – Reference guides
    – Tutorials and training
 Students
 Colleagues (Tech Team Members)
 Technology coordinator
    What’s Wrong With
Depending on the Technology
 They may not be available at the moment you
  need help.
 There are numerous responsibilities of the tech
  coord besides supporting users. (E-rate, licensing,
  state reports, security, networking, planning and
  procurement, etc.)
 Your knowledge and skills don’t increase if
  someone else fixes all of your problems for you.
Why take responsibility for my
  classroom computers?
 You’ll be a wonderful role model for your students (and
 You’ll develop a better understanding of the
  computer/network setup
 You’ll have less frustration for a small time investment
 You’ll be more confident using computers with your class
 You’ll use the computer more frequently and want your
  students to also
 You’re a lifelong learner
          Not Dependency but
 Your technology staff needs you to work WITH
  them to solve problems.
 By analyzing (troubleshooting) the situation and
  clearly describing what is wrong you can help
  speed the resolution process.
    – Ex. : not “my monitor isn’t working” but rather “I’ve
      followed the instructions at Kathy’s web site and
      checked the power and monitor cables, and the screen
      is dark even though the on light is green”.
    Use Basic Problem Solving
 Define the problem
 Identify options
 Identify best solution
 Plan and implement solution
 Evaluate the outcomes
   What is the scope of the problem?
    – Whole system is down / one component / no
      connectivity / etc
   What is the environment of the problem?
    – Machine ID / make, model / operating system /
      software involved / etc
   What is the impact of the problem?
    – Who is affected / potential program impact / etc
           Identify Options
 Has this occurred in the past? If so, are you
  able to correct the problem?
 Is there a temporary work around to the
 Can you submit a request for help via
  email? (use a lab computer if necessary)
      Identify the Best Solution
   Perhaps the process of analyzing the
    problem will uncover a simple solution, or
    one worth trying first.

   Always have a plan B.
 Plan and Implement Solution
 Be cautious and sensible, but don’t be timid.
 Have some confidence in yourself.
 Note each step of your solution in case you
  have to repeat it or relay them to someone
       Evaluate the Outcomes
   Did you fix it? If no, go to Plan B

   If you did fix it, file away your solution
    steps for future reference.
     Know What You Know..
 Inventory your skills related to various
  technology subjects.
 Test yourself. Set up practice scenarios and
  work your way through them.
 Use tools such as assessment tests and
  certification programs to verify your skills
  and knowledge.
Build a Partnership with Tech
 Thoroughly understand your district’s
  technology problem reporting and
  procedures…and follow them.
 Take advantage of opportunities to learn
  about your computing environment when
  you are NOT experiencing a problem. Read
  some of the topics at
    Participate in Knowledge
       Building Activities
 Internet –
 NWOCA (resource visits and workshops)
 Building Tech Teams
 Professional Development opportunities
 Books in building (especially about
  integrating technology into curriculum)
 Books in local libraries
NO, I’m not too dependent on
 Otsego’s technology staff!
 I’m willing to accept some
  responsibility for my classroom
  computers, including troubleshooting.
 I’m able to communicate details via
  email to Craig.
 I’m a lifelong learner, even when it
  comes to technology!

To top