The email arrives on a Monday. The person who handled the website gave notice on Friday, and somewhere between the calendar invites and the budget review sits a message from your boss: "You're good with technology. Can you take over the website until we figure something out?" By Wednesday you have a password document of uncertain age, a hosting invoice from a company you have never heard of, and a login that no longer works. Some version of this scene plays out in offices, shops, and nonprofits every week.
The purpose of this post is to explain why the role lands this way, why the absence of training is structural rather than personal, and why the qualities that caused the job to find you are the qualifications it actually requires. That argument matters, because the most common reason capable people manage a website badly is not lack of skill. It is the belief that they are unqualified for a job they are already doing.
How the role lands on people
Digital responsibilities accumulate in organizations the way boxes accumulate in a storage closet: one at a time, each for a good reason, with nobody assigned to keep track of the whole. A domain gets registered for a product launch. Someone signs up for an email marketing account during a fundraising push. An intern creates the Instagram profile. A contractor builds the website and hands over a login that gets forwarded twice and then forgotten. None of those decisions was wrong. Over a decade of them, though, the organization ends up renting a dozen digital properties with no landlord of record.
When the one person who understood most of it leaves, the responsibility flows downhill to whoever is nearest and most capable. That is usually the person who fixed the printer, built the mail merge, or answered the last "is the website down?" question. This role is rarely posted, rarely trained for, and almost never comes with a manual, yet nearly every organization with a digital presence has someone doing some version of it.
Why nobody trained you
There is a structural reason, and understanding it will spare you some resentment. In a small organization, web management spans marketing, information technology (IT), legal, and operations all at once, which means it belongs cleanly to no department and no job description. Hiring for it rarely pencils out: the work is real but rarely full-time, so leadership reasonably concludes that someone here can absorb it. Training programs exist for marketers, for IT staff, and for developers; none of them covers the person holding all three ends of the rope part-time.
While the missing training is real, it is also less of a gap than it feels. The technical knowledge this role requires can be acquired one topic at a time, in the order your situation demands. What cannot be taught nearly as easily is conscientiousness, and the role found you precisely because you have it. Organization, communication, follow-through, and a willingness to read the instructions are the actual qualifications. The rest is a reading list.
What the job actually is
A web manager is the person responsible for the strategic and operational oversight of an organization's entire digital presence: the website, the domain names, the hosting account, the business email, the social profiles, the analytics, the software subscriptions, and the payment tools connected to all of it. Stated plainly, the job comes down to three duties. The first is risk reduction: the domain renews, the backups exist, the passwords belong to the organization rather than to a departed employee, and the site does not invite legal trouble. The second is continuity: everything keeps working through staff changes, vendor changes, and your own eventual vacation, which means documentation someone else could follow without you. The third is steady improvement: the digital presence serves the mission a little better each quarter.
Notice what is not on that list. Writing code is not the job. Designing graphics is not the job. Fixing laptops is not the job, even though the "good with technology" reputation will attract those requests. These are crafts you can rent by the hour, and renting them is usually the right call. A useful way to hold the role is to think like a property manager rather than a builder: someone who knows what the portfolio contains, when every lease renews, which contractors to call, and which building needs attention next.
The honest tradeoff
One observation belongs here, because you may be telling yourself this arrangement is temporary. In my experience, it almost never is. Organizations that hand this role to a capable person rarely take it back, because the arrangement works. The choice in front of you is not whether to hold the role but whether to hold it by accident or on purpose: reactively, one small crisis at a time, or strategically, with an inventory, a plan, and a paper trail. The reactive version costs more, in hours and in outages, and it never gets easier. The strategic version is front-loaded: a hard first month, then quiet quarters.
Strategist first, technician second
Given all of that, the defining question of the role is not "can I learn to do all of this?" It is "how should each of these get done, and by whom?" Your value to the organization is judgment. The framework I recommend is decide, delegate, automate. Decide covers the judgments only you and your leadership can make: what the organization owns and under whose name, what the budget is, how much risk is acceptable, what the website is for. Delegate covers skilled work others do better and faster: code, design, copy at volume, specialized security response. Automate covers the repeatable and forgettable: renewal reminders, backups, uptime monitoring. One caution rides along with the third item. Automation is not abdication; a backup that has never been test-restored is a hope, not a plan.
Where to start this week
Two recommendations. First, write the one-sentence version of your job description and send it to your boss or board for confirmation. A serviceable pattern: "I am responsible for keeping our digital presence (website, domains, email, and connected accounts) secure, current, and serving the organization's mission, with a budget and vendors to match." The reply you get back is your first piece of role documentation. File it. Second, before you improve anything visible, find out what the organization actually owns online. Every risk described above lives in an account you have not found yet, and next week's posts walk through that inventory step by step.
The role may have arrived by accident. Holding it well is a decision, and it is one you are already qualified to make. The full argument, and the chapters that follow from it, are in Strategic Web Management: First Steps for the Accidental Web Manager. The free companion worksheets arrive by email, signup today!