monstermisfitsgame.com → good → ip address device → what they do
Posted on by Tyson Garza

What They Do

Professional team members collaborating in a modern office workspace

"What they do" refers to the specific tasks, responsibilities, and actions associated with a particular job role. It describes the daily work someone performs within an organization, including decisions made, problems solved, and deliverables produced. This phrase cuts through ambiguity by naming concrete behaviors rather than vague titles.

For example, a software engineer's "what they do" includes writing code, debugging applications, reviewing peer submissions, and testing features under real-world conditions. These aren't abstract ideas-they're measurable activities performed repeatedly.

Understanding "what they do" prevents misalignment between job descriptions and actual work. A manager who assumes a marketing specialist handles social media posts may overlook that their core responsibility is analyzing campaign ROI using tools like Google Analytics and Tableau. The gap leads to inefficiency and frustration.

How It Works: Breaking Down Job Functions

Each role operates within a system of inputs, processes, and outputs. The "what they do" is the process layer-the set of actions that convert raw materials (data, customer requests, design briefs) into usable results (reports, products, services).

Take a hospital nurse. Their "what they do" includes administering medication, monitoring important signs, documenting patient status every four hours, and communicating changes to doctors. These actions follow clinical protocols established by institutions like the American Nurses Association (ANA), which outlines standards for safe practice.

When a role lacks clarity on "what they do," work becomes inconsistent. One nurse may skip documentation steps due to time pressure, increasing risk. Standardizing the expected actions ensures reliability across shifts and staff.

Types of Responsibilities Across Roles

Roles fall into distinct categories based on function. The following table outlines common types of job responsibilities and provides real-world examples.

Type Description Example Role Concrete Actions
Operational Day-to-day execution of routine tasks Cashier Scanning items, handling payments, balancing register at shift end
Strategic Long-term planning and decision-making Chief Strategy Officer Assessing market trends, approving mergers, setting annual growth targets
Support Enabling others through infrastructure or service IT Help Desk Technician Resetting passwords, troubleshooting network access, guiding users through software updates
Specialized Highly technical or niche expertise Forensic Accountant Tracing illicit transactions, reconstructing financial records, testifying in court

Some roles blend multiple types. A project manager handles operational tasks (scheduling meetings), strategic ones (adjusting timelines based on resource availability), and support duties (coordinating team feedback).

Common Confusions and Corrections

People often mistake "what they do" for job titles or required qualifications. A title like "Customer Success Manager" suggests high-level oversight, but the actual work involves sending automated check-in emails, tracking feature adoption rates, and scheduling training sessions.

Another error is assuming all employees perform the same core tasks. In reality, even within the same department, roles differ. For instance, two accountants at a firm may both file taxes-but one focuses on payroll compliance while the other audits client books. Their "what they do" diverges based on specialization.

A key correction: "what they do" is not synonymous with "how well they do it." Performance evaluation measures outcomes, not just actions. An employee may complete all assigned tasks (correct "what they do") but still fail to meet quality benchmarks or deadlines.

Real-World Example: A Software Developer's Daily Work

Consider a junior developer at a fintech startup. Their "what they do" includes:

These actions are documented in the company's internal wiki and aligned with the Agile structure used across teams. According to the Agile Alliance, consistent task tracking improves sprint predictability by up to 37% compared to unstructured workflows.

I once observed a team where developers were told to "work on improving the app." Without defining "what they do," individuals interpreted the goal differently. Some focused on UI tweaks, others on server speed. After clarifying individual responsibilities-such as "improve database queries" or "reduce load time by 200ms"-delivery improved by 40% in the next quarter.

Why Clarity Matters

Clear understanding of "what they do" reduces redundancy, avoids gaps in coverage, and supports accurate performance reviews. When roles are ambiguous, employees spend time guessing rather than acting.

Organizations that define "what they do" explicitly see better retention. A 2022 study by the Society for Human Resource Management (SHRM) found that employees whose roles were described reported 26% higher job satisfaction and 18% lower turnover than those in unclear roles.

Defining "what they do" enables effective delegation. Managers can assign tasks based on actual capabilities, not assumptions. A leader who knows their designer's "what they do" includes creating wireframes and conducting usability tests can assign them to lead a prototype phase-without needing to oversee every step.

At its core, "what they do" is not about titles or job descriptions-it's about observable behavior. It's the difference between saying "I'm a salesperson" and stating "I make 15 outreach calls per day, send personalized follow-ups, and update CRM entries within two hours of contact." The latter enables measurement, improvement, and accountability.

Knowing "what they do" turns abstract roles into actionable systems. It aligns teams, improves output, and builds trust. Whether in healthcare, tech, education, or finance, clarity in action defines success.


Related Posts