My contribution to a board
I could help directors examine the conditions behind a technology claim. A clean test report may be useful, but it should explain the configuration, the population tested and the consequence of an unresolved exception. My experience is in bringing that account into an investment or release discussion without asking non-specialists to reproduce the experiment. I would also ask who owns acceptance of the complete product and whether the company's promise extends beyond its evidence. For example, software behaviour under interrupted power belongs alongside the recovery service model and component cost. That relationship is more useful to a board than a long list of technical activities. I would learn the company's customer obligations first and avoid importing Pelvori's methods as universal rules, especially where another business has a different product responsibility or risk profile.
Judgement in practice
01An expensive recovery path with an explicit owner
The update redesign cost ₹48 lakh in engineering and added ₹180 to the client's estimated device components. I supported discussing that expense openly rather than treating recoverability as a technical improvement whose commercial effect could be left for later. The repeated interruption matrix passed, but the client still owned complete-product acceptance. As a director I would ask management whether the investment paper joins those elements: the failure being addressed, the recovery expectation, the cost and the authority accepting the remaining uncertainty. I would not approve a particular firmware mechanism from the board table. My contribution would be to make sure the business decision is informed by the engineering evidence and that a successful experiment has not been mistaken for a wider assurance.
02The better headline was the rejected experiment
The 46% compression result looked stronger than the selected 27% result until the processing-time cost was considered. I kept the rejected candidate in the engineering record and the chosen configuration in the benefit summary. That experience would make me ask a board paper whether its headline describes the solution actually adopted and whether improvement in one resource has moved cost elsewhere. The relevant trade-off depends on the business and device; it cannot be settled by choosing the largest percentage. I would also ask whether management has inferred financial or battery benefits that the experiment did not measure. Clear reporting should help directors compare the actual alternatives without becoming a substitute for the specialist acceptance work still required.
My first year on a board
My first year would begin with induction into the company's products, customers, financial model and responsibilities across its supply chain. I would read past investment decisions and significant incidents to understand how management reports uncertainty, including where an apparently successful project later created an obligation. Meetings with engineering and commercial leaders should happen through the agreed board process and help me learn, not create a parallel chain of instructions. I would look for a small number of material questions where the board needs better clarity about evidence, acceptance and continuing cost. I would also ask the chair for feedback on whether my contributions are proportionate and understandable to colleagues from other disciplines. By the end of the year I would want to demonstrate better questions and better collective understanding, rather than count the technical details I had added to board papers. One early discussion would examine how sales commitments are checked against engineering evidence before a contract is agreed. I would ask which assumptions can be changed by management, which require the customer’s acceptance and how an unresolved technical issue reaches the appropriate decision-maker. That would help me understand the company’s actual governance of product promises instead of relying on the formal reporting chart alone.
Conflicts and their management
The review would need to cover Pelvori, Dorvellen Embedded Group, their customers, suppliers and other interests relevant to the opportunity. I would disclose personal interests and family connections and obtain employer consent before accepting a role. Technical knowledge can itself create a difficult boundary: a prospective company should not expect me to share customer designs, confidential methods or information obtained through my executive position. Recusal may resolve an occasional issue, but repeated exclusion from the central product discussion could make the appointment unsuitable. I would discuss that possibility before joining rather than assume it can always be managed later. The relationship review should be renewed when the business changes, and the chair should be informed promptly of a new connection that could affect my contribution or eligibility.
My independence statement
My eligibility for an external appointment would require examination of the particular company and the applicable legal position. I would disclose my employment, interests, group relationships and relevant family connections rather than assume that a separate employer establishes independence. The Companies Act and any applicable listed-company requirements, committee qualifications and limits on appointments would need to be considered by the company with appropriate advice. I am preparing for a possible role, not declaring that every condition has already been met. My technical experience can inform a nomination discussion but cannot replace the required assessment.
Committee contribution
Chair and member readiness| Capacity | Committees |
|---|
| Ready to join | Technology or product-risk committee discussions, where appropriate to the company |
|---|
Board and committee exposure
Presented to the Board or a committee
Pelvori Embedded Systems
Board engineering-investment and product-risk discussions
April 2022 – Present
I present selected engineering investment and material delivery-risk matters when invited, including the cost of the update redesign and the limitations of validation evidence. My role is to explain management's proposal and answer questions, then carry out the authorised engineering work. I have not served as a director or a board committee member. Exposure to those discussions has helped me understand why a technical result needs an economic and contractual context, but it is not equivalent to experience making collective board decisions.
Capacity and preferences
- Time available
- 18 days per year
- Current directorships
- 0
- Sectors
- Engineering-services businesses · Industrial software · Specialist electronics services
- Company type
- Established private companies with a meaningful engineering-risk agenda
- Company stage
- Businesses strengthening product development, technical investment and the quality of release decisions
The seat I am pursuing
I am interested in one first external non-executive appointment whose specific category and conditions would be determined through the proper process. I have no current directorships and would initially contribute as a member to relevant technology or product-risk work rather than seek to chair a committee. Eighteen days annually is my provisional capacity, subject to induction, travel, meeting preparation and exceptional demands being assessed with my employer and the proposed board. I would prefer a company that wants thoughtful challenge of its engineering commitments, not a prominent title attached to an informal consulting arrangement. If the actual workload or conflicts exceed what I can responsibly accommodate, I would decline the opportunity rather than rely on an optimistic calendar.
Governance learning and readiness
IICA Independent Directors’ Databank: Not yet registered
This fictional profile records governance preparation before databank registration. I have neither registered nor claimed a proficiency-assessment pass or exemption. Before taking an Indian independent-director opportunity forward, I would establish and complete the applicable databank requirements as part of the company's appointment process. The website should not imply that study alone has conferred a status I do not hold.
- I am studying how directors assess risk appetite, challenge management and make collective decisions. I am particularly interested in the point at which an engineering exception becomes material to the business rather than simply another project issue. My notes distinguish asking for a credible account from trying to run the validation programme through a committee.
- I am also strengthening my understanding of financial statements, investment appraisal and contractual exposure. An engineering decision can change a component cost, a service obligation or the timing of revenue, and a director needs to connect those effects. This learning does not make me an accountant or legal adviser, and I would expect the board to retain the appropriate complementary expertise.