Connecting Teachers
to Technology
|
 |
|
| In This Section |
|
|
|
|
|
Technology Coordinator's Forum at Seven Hills School
August 25, 1997
Late-Morning Activity:
Defining a Technology Coordinator's Job Description
One of our Forum's participants is about to begin a
new part-time position as a technology coordinator. We came together
to discuss what the typical "job description" usually is, and what
it, indeed, should be.
Here's Our Brainstormed List of a Typical
Technology Coordinator's Job Description (whew!!):
- Prepare technology budget
- Ordering software and hardware
- Installing software and hardware
- Maintaining software and hardware
- Inventory
- Staff support
- Finding your champions (students, teachers,
tech support, etc.)
- Research & keeping up with reading,
surfing the net, previewing software
- Develop surveys, scope & sequence
- Site tech plan: develop & update
- Presentations to staff, PTA, district council,
board, etc. (Can also give input or delegate)
- Find curriculum resources for teachers
- Troubleshooting
- Work with student groups
- Attend conference and workshops
- Network management
- Develop/maintain web site
- Community liason
- Grant writer & fundraiser
- P.R.
- District Liason
How do we get real about this crazy list?
Here are some comments:
- The title "technology coordinator" implies that
this one person coordinates everything, but doesn't necessarily
do
everything.
- The job of technology coordinator has to be
team-based. Finding the champions & developing a team is
essential.
- It isn't realistic for one person to do
everything, especially if it's in addition to teaching regular
classes. This is truly 2 full-time jobs.
- Let's figure out what is realistic and given
all the constraints, what would be the best order of priority for
these various roles.
- What roles are inappropriate for you and
should be handled by someone else?
Our Collectively Defined Job
Description:
PART I: Things you want to DO:
(You need to be the one doing these
things)
- Develop technology team (visionaries, people
onsite, troubleshooters, people you can delegate pieces to)
- Define a technology plan
- Communicate your priorities to others
- Delegate pieces to your technology team
- Act as liaison for implementing technology
plan
- Finding champions ("special friends,"
visionaries, parents, community)
- Staff development (could also be
delegated)
- Presentations to staff, PTA, district council,
board, etc. (Can also give input or delegate)
- Community/Parent/Staff/District/Board
Liaison
- Attend conferences & workshops
- Research & development (could also be
delegated)
PART II: Things you want INPUT
on:
(You don't have the ultimate
responsibility, but you want to be consulted & involved)
- Define technology plan
- Define technology goals
- Prepare budgets
- Develop Acceptable Use Policies
- Develop Scope and Sequence
- Write grants
- Preview equipment & software (could also
be delegated)
- Order, install and maintain equipment &
software (could also be delegated)
PART III: Things you want to
DELEGATE or COORDINATE:
(You are responsible for these things,
but other people can do them.
This is why you built a team of supporters & champions!)
- Troubleshoot problems
- Take inventory
- Manage network
- Develop and maintain web site
- Provide parent & community classes
- Run a student group
[ Getting to Know Each
Other | Role Plays |
Job Description | Commandments
]
[ Camp
Main Page | Computer Strategies
Home | Email
Us! ]
|