Finding My Place in the Wild Web Estate
After a month in my role as Web Governance Administrator, I thought it appropriate to reflect and share a little about my experience so far (prior to the events of the PHP incident, that deserves it’s own post)!
A Weeklong Handover
After my interview and first day, I started getting an idea of what my job would entail – or at least, I had a good idea of the overall project of the team I was on: taming the “Wild Web Estate”.
My manager, Stratos, let me know that this job had a steep learning curve and that there would be a lot of information handed over to me from Angelina, the student previously in my role. He warned that the four days I had left before Angelina’s last day might not be enough for her to impart all her knowledge and pass what she had been working on over to me.
We finished the handover sheet they had put together and went through all my questions in about three hours. The rest of my time with her was spent going through and helping her finish her big tagging project – and, perfectly, we finished about 30 minutes before the end of her last day.
“My experience as a Web Governance Admin Intern” – Blog post by Angelina Lai.
Of course, this experience using the software and having her next to me while I went through the process myself was incredibly useful for when questions popped up that I wouldn’t have thought to ask. So, I am glad the handover form didn’t take as much time as we had planned.
After finishing the handover and project with Angelina, my expectations of my role changed significantly. I was then under the impression that my job would be very similar to other student roles I have seen or held in the past: heavily supervised, with little flexibility or say in what I’m working on. I would be given a task, complete it, and hand it back to my manager – for lack of better terminology, “busy work” that’s necessary for the project to be completed. (Spoiler alert: I was wrong.)
More Than Just a Student Role
At this point, I thought that if I couldn’t get much professional development from my role, I would at least do my best to reach out to others in the larger group to make connections, get a better understanding of the overall strategy of the Information Services Group, and learn more about my colleagues’ and superiors’ backgrounds and how they got into the roles they’re in now.
These kinds of 1:1 meetings were extremely common in my previous corporate roles, so in my next 1:1 with Stratos, I went in ready to hear what my next assignment was and brought up the question: Is this kind of connecting with coworkers common here, and what is the proper etiquette around it?
With the contents of this meeting and his response to that question, my expectations changed yet again.
He informed me that he wanted to start bringing me into the larger project, rather than just giving me assignments to work on and then submit, as I had previously assumed. He also let me know that he had already started scheduling introductions with a lot of people I would be working with, and that having him in those meetings would help give both me and my new colleagues context for where we each fit into one another’s roles and the overall project.
This wasn’t something my previous supervisors had taken the time to do, and I was, and still am, incredibly grateful.
Finding My Voice
That 1:1 with Stratos started a series of discoveries for me over the following weeks about how much flexibility and freedom I had to bring my own ideas and thoughts into my role.
I started attending meetings and conferences, like the “10-year digital estate plan” and speaking with more colleagues. As I gained a more all-encompassing understanding of not only what we were trying to do, but also the obstacles that stood in our way, I slowly, little by little, started pushing the self-inflicted boundaries of my role.
The final turning point for me was yet another weekly 1:1 with Stratos that we had to extend by over an hour to cover all the thoughts, questions, and ideas I had around our project.
That conversation was probably the most productive work meeting I’ve ever had, in the sense that it was an incredibly informative conversation where I was able to fully understand the challenges and boundaries of our project, challenge the assumptions we had, and ask questions to help us think about the project differently.
It was really the first meeting in a corporate setting where I felt like my thoughts and opinions were taken seriously and valued. We talked about my self-inflicted restrictions and set clear expectations around the freedom I had to problem-solve, generate ideas, and give opinions and input on our project.
Putting Ideas Into Action (Behind the Scenes of the Wild Web Estate)
Since then, I have thoroughly enjoyed being an active participant in conversations around the strategy, planning, and implementation of the “Wild West Web Estate” project.
“2,117 websites and counting: welcome to our Wild West Web Estate” – Blog post by Stratos Filalithis
We worked to define the scope of my work, which entails taking all the work Angelina did in tagging websites in Little Forest (the software for documenting website information for maintaining the web estate), exporting the data, and formatting it in a functional way to give to the respective IT departments. They will then fill in missing information, correct inaccurate information, and make active decisions on whether to keep, fix, or retire these websites. I will then format their responses and update Little Forest with these actionable insights.
Building Something That Lasts
There is one thing I have noticed, however, that will be a bit of a challenge in my role.
Building out the tools I’ve alluded to in this project and making them reusable to sustain the practice we are implementing is actually fairly straightforward. With the flexibility and ability to really contribute my own ideas to the implementation and customisation of these tools, I’m able to bring my own vision to life.
However, my role isn’t permanent. As of now, I’m only planning to be in the UK for a year while I finish my studies.
This adds an additional layer to the project: How can I make these tools and processes sustainable and usable by someone else who might not have my technical background – especially when it comes to the aspects of my job that involve data management, restructuring, and organisation through coding?
It’s an interesting line to walk between making this process as efficient as possible with the tools I know how to use and making it usable for the next person in my position with minimal training on the process.
This challenge, though, only adds to my excitement about both this specific project and this role as a whole.
Leaving My Mark
I can’t begin to describe (although it may have been evident above) how pleased I am with my role and the support I have, specifically from Stratos and my other colleagues, to be a genuine thought partner throughout this project.
My biggest goal, beyond professional development, is to leave behind a legacy – my input written, either figuratively or literally, into these tools and processes that will hopefully be used for many years to come.
