Amy, this is a great article. I’ve been given the space to be both a techie and a leader in our org (only 6 staff doing statewide work), and we’re moving toward codifying that role a little more clearly for me.
The most important thing that I think a techie-leader helps us do as an org is to make sure we are not “leading with the tools.” Because I am involved in project development and management, and am involved in conversations about content generation, I can look at a project and see what tools might make it easier, rather than coming in from the outside with “Hey, can we build a wiki?” with no good reason to build a wiki (which is why we don’t have one).
Also, when you’re a tiny org with limited capacity, trying to do a lot of work, it’s essential to always ask “Is there a tech tool that could make this project more manageable? More possible? Cost less?” and my org makes the space for me to be able to ask those questions. We all benefit from that.
COMMENTS
BY Johanna Bates
ON April 15, 2008 10:48 AM
Amy, this is a great article. I’ve been given the space to be both a techie and a leader in our org (only 6 staff doing statewide work), and we’re moving toward codifying that role a little more clearly for me.
The most important thing that I think a techie-leader helps us do as an org is to make sure we are not “leading with the tools.” Because I am involved in project development and management, and am involved in conversations about content generation, I can look at a project and see what tools might make it easier, rather than coming in from the outside with “Hey, can we build a wiki?” with no good reason to build a wiki (which is why we don’t have one).
Also, when you’re a tiny org with limited capacity, trying to do a lot of work, it’s essential to always ask “Is there a tech tool that could make this project more manageable? More possible? Cost less?” and my org makes the space for me to be able to ask those questions. We all benefit from that.