Governance Bodies & Operating Rhythm

This document explains how TechAbout makes and records decisions: the meetings we hold, the standing groups that own recurring judgement calls, and how goals flow from the company down to each person. It is for every employee and leader, and it is public — clients and candidates are welcome to read it.

Our operating rhythm

TechAbout runs on a predictable cadence. Fixed rhythms mean fewer surprise meetings, clearer priorities, and a shared sense of where things stand. Each forum below has a defined purpose, a rough duration, and an owner who keeps it on track. Attendance is scoped to who actually needs to be there — we protect focus time as deliberately as we protect these meetings.

• Daily stand-up — a short, same-time check-in within each team. You share what you shipped, what you are doing next, and where you are blocked. It exists to surface blockers fast, not for status theatre. If a topic needs real discussion, take it offline.
• Weekly team sync — each team (engineering, SEO and content, design, security, sales and Express operations, and People/Admin) reviews its work-in-progress, priorities for the week, and anything at risk.
• Weekly leadership meeting — leads and role-owners align on cross-team priorities, unblock decisions that span teams, and agree who owns what for the week ahead.
• Monthly business review — a look back and a look forward: delivery health, client and pipeline signals, hiring, security posture, and progress against quarterly goals.
• Quarterly planning and OKRs — we set the next quarter's objectives, review how the last quarter landed, and reset priorities across the company.

Standing groups

Some decisions recur often enough to deserve a permanent owner rather than an ad-hoc scramble. These groups meet on their own schedule or convene when triggered, and their outcomes flow back into the rhythm above. Because the team is small and scaling, one person may currently own more than one of these groups until the team grows.

Leadership team

The leadership team sets company direction, owns the OKRs, allocates budget and resources, and makes the calls that cross team boundaries. The specific C-suite and lead roles that make up this group are described in the individual charters elsewhere in this book.

Hiring

Hiring decisions are made by the People function together with the hiring manager for each role, running through our ATS pipeline in ERPNext. For how roles are opened, screened, and closed, see Employment Practices & Placements. Candidate questions go to careers@techabout.com.

Security and incidents

Security matters and suspected incidents route to the security owner via security@techabout.com. When something is triggered — a suspected breach, a data-exposure risk, or a serious client-facing outage — this group convenes on demand to contain, assess, and communicate, regardless of the normal calendar.

Ethics and whistleblowing

Concerns about conduct, integrity, or wrongdoing go to ethics@techabout.com, and are handled confidentially. For everyday workplace concerns and how to raise them, see Grievance & Complaint Escalation and the Code of Conduct.

How goals cascade: OKRs

We plan with OKRs — Objectives (what we want to achieve) paired with Key Results (the measurable outcomes that prove we got there). Goals cascade so that everyone's work ladders up to the same few priorities:

1. Company OKRs are set by the leadership team each quarter.
2. Team OKRs translate those into what each team will deliver.
3. Individual goals connect your work to your team's OKRs, and are reviewed through the normal cycle in Performance Appraisal.

If your work doesn't ladder up to a team objective, treat that as a signal to raise — either the goal is missing or the work needs re-prioritising.

Deciding out loud, writing it down

Our rule is simple: no important decision should live only in someone's head or a private chat. Decisions are recorded where the people affected can find them.

• Every decision forum has a note-taker. Decisions, owners, and next steps are written down — not just the discussion.
• Decisions and their reasoning live in the relevant ERPNext record, shared doc, or team channel, and are linked so the trail is followable later.
• We name a single owner for each decision — the person accountable for it happening — even when a group made the call.
• Outcomes that affect the whole company are communicated in the monthly business review and in writing, so nobody has to have been in the room to stay informed.

This is how a small, scaling team stays fast without losing the thread: clear rhythms, clear owners, and a written record anyone can catch up on.

Questions? Contact hr@techabout.com.