All field notes

Leadership · Retrospective

Handing on a studio: what I would want any successor to find

An open box holding a key, a folded document and a small blue notebook.
Concept illustration · AI-generated

My 2021–2025 chapter at Playermon is over. I joined in 2021 as a blockchain developer, completed the smart contract and led the token-sale promotion campaign, and became CEO around September that year. The studio reached more than 60 people at its peak. My time there concluded this year, following the company's acquisition. What Playermon became after the handover is their chapter, not mine.

This post is not about the handover. It is about a list I have been writing for myself this month: what any studio should be able to give whoever runs it next, whether that is a new leadership team or the same team a year later with half its memory gone.

I have been on the receiving end of this before. At Trivechain I took over maintaining the protocol in 2019, after the developers who first built it had stopped. I know what it is like to inherit a live system from people who are no longer there to ask.

Contracts, and what each one controls

A blockchain studio's most lasting decisions are deployed. During my time, Playermon's contracts came to span more than one chain. The Playermon NFTs and the marketplace were on Polygon, and item NFTs under ERC-1155 became tradable there in December 2023. PYM went to Solana in March 2024, with the original token remaining on Polygon. In October 2024 Planet Invasion launched as a Telegram mini-app.

For each contract, a successor needs its address, the source it was verified against, who holds each privileged role, and what that role can do. Can it mint, pause, change a fee, or replace the code? A contract nobody can administer is safe until the day it needs a fix. A contract whose administrator nobody can name is worse.

Keys, and a record of what they signed

In March 2024 the published plan was to lock 100 million PYM in a Safe on Polygon. A multisig spreads control across several signers, but it does not explain itself. A successor should find the signer set, the threshold, where each key is held, and a log of what every past transaction was for. None of that belongs in public. All of it belongs somewhere the next person can reach on their first day.

Keys are not only on-chain. Domain registrations, cloud accounts, app listings and the administrator rights in community channels are keys too, and they are easier to forget because nobody thinks of them as custody.

Promises already made in public

A studio's public record is full of commitments with dates on them. In January 2022 I wrote that team tokens would vest over ten years. When PYM went to Solana, the published plan said nothing would be distributed there for three months. By September 2024 holders had voted on six proposals through the studio's DAO, covering questions such as a giveaway that bots had gamed, leaderboard rewards and how often Happy Hour should run.

A successor should find all of these in one list, each with its source and date, so that nobody has to reconstruct them from old posts or learn about one for the first time from a holder in a chat.

Channels, and who can speak in them

In January 2023 we merged our language groups into one Telegram forum. In December 2024 the team previewed Razortooth AI, an in-house agent that took part in the community chat and helped monitor the group. I oversaw that work.

A community channel is also a set of permissions: who the administrators are, who can pin an announcement, which bots can post, and what each bot is allowed to do. When people leave, those permissions should change with them, on purpose and on a known date, rather than whenever someone notices.

The reasons, not only the decisions

The most useful thing anyone leaving can hand over is why. When our marketplace opened in December 2021, we said in public why it priced NFTs in MATIC rather than in PYM. In the fifty-day update in January 2022 I wrote down what had slipped as well as what had shipped, and turned the roadmap into a to-do list reviewed every fourteen days. Patch notes, tutorials and the whitepaper's roadmap carry the same kind of record.

A decision without its reason tends to be reversed by someone who cannot see what it was protecting against. A studio that reached more than sixty people holds most of its knowledge in people, not documents, and people move on. Writing the reasons down is how some of that knowledge stays.

Roles are meant to move

At the Malaysia Blockchain Association, the Vice President seat I had held since 2019 passed to another member at this year's AGM, and I became Treasurer. It was a reminder that a role is held for a time, and that its real test is whether the next person can pick it up.

This list is what I would want to find if I were the one arriving. I think it is also a fair test of anyone who leads something: could a stranger run it next month from what you have left behind?