Dev ParameshvanChief Human Resources Officer

The boardroom

Oversight should examine the organisation behind the operating promise.

A pharmaceutical board should be able to ask whether the organisation makes its technical responsibilities workable. That question is broader than the number of vacancies filled and more specific than a general discussion of culture. It concerns the authority attached to a role, the careers through which expertise is developed and the employment assumptions behind an operating plan. I would contribute to that discussion from a people-leadership background while recognising the limits of my technical knowledge.

I have presented executive recommendations to a nomination and remuneration committee since 2018. I have not served as a director. The distinction matters because a recommendation can be detailed and still leave the board with questions about alternatives, incentives and the wider enterprise. My preparation for a first board role includes learning to ask those questions without slipping into the management task I know best. A director should not become an additional line manager merely because the subject is familiar.

Specialist progression offers one example. Management may propose a new career structure and explain the expected benefits. The board can ask what contribution the roles are intended to create, how the assessment will be governed and what cost is being approved. It should understand whether technical leaders own the relevant judgements and whether unsuccessful employees receive a credible explanation. It need not decide each person’s grade. The oversight question is whether the process and the employment investment are consistent with the company’s needs and responsibilities.

An expansion plan raises another set of questions. The proposed headcount may look economical because it relies on internal transfers. Directors should be able to see what experience those moves remove from existing operations and what transition support has been funded. The distinction between a completed appointment and technical readiness should remain visible. I would ask management to explain the dependency and its effect on cost and timing, rather than suggest that the board can resolve it by demanding a more optimistic recruitment report.

The quality-function case illustrates the need to examine authority in practice. A formal reporting line can coexist with uncertainty about who participates in appointments, reviews or staffing decisions. Adding another line may create coordination problems without improving the arrangement. The board should ask how unresolved matters reach the right decision-maker and what evidence shows that the process is working. A low number of escalations is not, by itself, proof that the underlying responsibilities are clear. It may also reflect an arrangement people do not find useful.

Reward design requires similar attention to interpretation. In the fictional attendance-award case, the people function supported a measure that encouraged an unwanted pressure around illness reporting. A board reviewing a material remuneration approach should understand how management has examined likely behaviour and how the scheme will be reviewed after use. If a defect is found, the response should include affected earlier decisions where appropriate. My own error makes me cautious about treating administrative simplicity as sufficient assurance that an incentive is sound.

I would also pay attention to confidentiality. Workforce information can help a board understand a material risk without exposing individual health, grievance or performance details unnecessarily. Management should provide material appropriate to the board’s responsibility through the company’s agreed processes. A director’s curiosity is not a reason to circulate personal material more widely. My contribution would be to ask whether the evidence supports the decision while respecting the responsibilities of those handling sensitive matters.

My suitability for any appointment would depend on the company and its circumstances. Current employment in pharmaceuticals creates relationships that would need disclosure and review, including potential commercial or recruitment conflicts. I would need employer consent, adequate time and preparation in the wider business, financial and governance responsibilities. I have not registered with the IICA databank and make no claim of automatic eligibility. I would address the applicable requirements with appropriate advice before participating in an independent-director appointment process.

The perspective I offer is therefore bounded. I know how employment structures can strengthen or frustrate the work a technical organisation depends on. I would bring that experience into collective oversight, listen to the board’s other expertise and remain accountable for the limits of my own. A useful first year would be measured by the relevance of my questions and the quality of the board’s judgement, not by the number of familiar people initiatives I could persuade management to adopt.

On governance

I pay attention to what happens to the person who gives an inconvenient technical answer. A company can praise expertise while making promotion depend on leaving it behind. My work is to make employment choices consistent with the responsibilities the business says it values, and to acknowledge where our own people systems have sent a different message.

Formation

Education & credentials

  • Bachelor of commerceVedasravan College1991

An invitation

Contact

I am open to a people-leadership or advisory mandate in a pharmaceutical business willing to examine the relationship between technical authority, careers and investment decisions. I would consider a first external board appointment with an appropriate induction and a clearly defined contribution. For speaking, I prefer a working discussion of one employment decision and its consequences to a general address on inspiration.

Open to
  • Board appointments
  • Advisory roles
  • Speaking invitations
  • Executive opportunities

office@devparameshvan.example