How TechAbout Is Governed

This is the opening document of TechAbout's Governance & Leadership book. It explains how decisions get made here, who is accountable for what, and where to look next. Every TechAbout employee is expected to read the handbook, and this book is part of it — whether you write code, close deals, design brands, or lead a team.

Governance sounds like something for boardrooms and lawyers. At TechAbout it means something simpler and more useful: everyone should be able to see how the company is run, who owns a given decision, and how to challenge a rule they think is wrong. We put this in writing so it does not depend on who happens to be in the room.

The Four Layers of Authority

TechAbout is organised into four layers. Accountability flows down — each layer sets direction and delegates authority to the one below it. Answerability flows up — each layer owes honest reporting, escalation of real risks, and results to the one above it. The diagram below shows how the two directions meet.

• Ownership & Board. The owners and any board members hold ultimate accountability for the company. They set its purpose and values, approve major strategy and significant financial commitments, and appoint the executive team. They govern in line with Pakistan's Companies Act 2017 and other applicable law; specifics here are general context only and are subject to review by qualified local counsel and current law.
• Executive / C-Suite. The executive layer turns the owners' direction into a running company. It owns strategy, budgets, hiring, and the health of each function — product and services, revenue, finance, technology, security, and people.
• Management / Department & Project Leads. Leads run the day-to-day. They own delivery for a department or a specific client project, set priorities within their remit, and are the first point of escalation for their teams.
• Teams & Individual Contributors. This is where the work happens — the code, campaigns, designs, security reviews, and client conversations that make TechAbout worth hiring. Contributors own their tasks and quality, and are trusted to raise problems early.

Our Governance Principles

Five principles sit underneath every charter and policy in this book. They are how we want TechAbout to feel to work in.

Clear ownership, decisions close to the work, everything in writing, leaders in service of their teams, and integrity that we never trade away.

1. One clearly accountable owner per decision. Every meaningful decision has exactly one name attached to it. Many people may advise; one person is answerable. If you cannot say who owns a decision, it is not ready to be made.
2. Decisions at the lowest capable level. Authority lives as close to the work as competence allows. We escalate for genuine risk, cost, or ambiguity — not for permission to do the job you were hired to do.
3. Transparency and written policy. If a rule matters, it is written down and readable. Undocumented rules are not rules; they are folklore, and folklore is unfair to whoever did not hear it.
4. Leaders serve their teams. A lead's job is to remove obstacles, give context, and make their people more effective — not to hoard information or decisions. Rank is a responsibility, not a privilege.
5. Integrity is non-negotiable. We do not cut ethical corners for a deadline, a client, or a number. This holds for how we treat clients, colleagues, data, and the internet assets in our care.

Roles Are Charters, Not People

Throughout this book, leadership roles are defined as charters — a written description of a role's mandate, decision rights, and boundaries. Charters describe the job, never the individual doing it. Because the team is small and scaling, one person may currently hold more than one role until we grow into separate ones. The charter still tells you what that role owns, whoever is wearing the hat today.

Where to Go Next

• To see how the layers connect and who reports to whom, read the organisation chart in this book.
• To understand who owns, approves, or is merely consulted on a given decision, read the decision-rights and RACI documents in this book.
• To understand a specific leadership role in depth, read that role's charter in this book.

Where this book touches everyday employee matters, it links to the existing handbook rather than repeating it — see the Code of Conduct, Grievance & Complaint Escalation, and Performance Appraisal.

Asking a Question or Proposing a Change

These policies are meant to be challenged when they stop serving us. If something here is unclear, outdated, or wrong, we want to hear it.

1. Raise it first with your lead, who can answer or route it.
2. To propose a specific change, write it down: name the policy, what should change, and why. Send it to hr@techabout.com.
3. The role that owns the policy reviews the proposal, decides, and — because transparency is a principle, not a slogan — explains the outcome.

Questions? Contact hr@techabout.com.