The review began at 2:00 in a small meeting room with no natural light. The employee was a pothos in a ceramic pot. Its manager, Simon, had brought it from the reception desk because the room was available and he believed in conducting difficult conversations away from the main office.
He placed the plant opposite him and opened a form. The plant leaned toward the glass panel in the door. Simon noted this as a possible concern about engagement.
“Let’s start with the positives,” he said. “You’ve been very consistent about being here.”
The plant had been at the company for eleven months. In that time it had not taken unauthorized leave, missed a call, or sent an email beginning “just circling back.” Its roots had remained inside the pot even during the office refurbishment, which several human employees had found difficult to do metaphorically.
Simon gave it four out of five for attendance. Five was reserved for exceptional performance, and he did not want to leave it with nowhere to grow.
Core responsibilities
The plant’s original role had been described as “bringing a bit of life to reception.” This had not been translated into measurable objectives. Simon acknowledged that the organization could have done better here. He had nevertheless formed the impression that the plant ought to be bringing more life than it currently was.
“You were quite full when you joined,” he said, turning the pot to inspect a bare section of stem. “There’s been some reduction.”
The reduction had followed a period during which watering responsibility moved from Facilities to Everyone. Everyone was a large and enthusiastic department with no named representative. On some days three people watered the plant. On other days the plant experienced a lengthy opportunity to develop resilience.
Simon wrote “inconsistent growth trajectory” on the form. He looked at the plant again. A leaf had turned yellow. This was disappointing, but it made the point easier to illustrate.
“We’d like to understand what support you need.”
The plant remained angled toward the door. Simon thought it might be asking for more visibility within the organization.
Collaboration and initiative
Feedback from colleagues had been broadly positive. Reception said the plant was pleasant to have around and did not create unnecessary work. Accounts described it as approachable. Someone from Sales had written “good energy,” which Simon appreciated even though he did not know how to incorporate it into the rating scale.
There was, however, a concern about initiative. The plant had waited for others to provide water rather than taking ownership of the issue. Simon understood that there might be practical limitations. He still felt that, after eleven months, it should have developed a more proactive relationship with its own wellbeing.
“Could you make your needs clearer?” he asked.
One leaf rested on the table. Simon moved it so it would not touch his laptop. The plant had produced that leaf during the brief period when somebody moved it beside a window. It was its largest and healthiest leaf. This seemed like the sort of positive behavior the organization should encourage, provided it did not interfere with the equipment.
He suggested that the plant identify three personal development goals before the next quarter. The plant leaned toward the faint borrowed light in the door panel. Simon interpreted the silence as thoughtful consideration.
The development plan
The agreed plan contained the word “agreed” because the template supplied it automatically. It asked the plant to improve fullness, maintain a positive presence, and demonstrate greater ownership of growth. Simon selected a target date six weeks away. He felt six weeks was supportive without being vague.
Under “resources required,” he wrote “to be confirmed.” He had intended to ask somebody about the watering arrangement, but the Facilities lead was on leave, and the conversation had already run over. It would be unfair to delay the plant’s development while waiting for an administrative answer.
He offered training. There was an online course on personal effectiveness, and he believed the recording could be placed on a tablet beside the pot. The plant’s ability to access the course would need to be discussed with IT. Simon made a note to investigate whether it required its own login.
The final rating was “meets expectations, with areas for improvement.” He read this aloud in a reassuring voice. The plant’s expectations had not been collected, but he was confident the wording provided a balanced account of the relationship.
Follow-up
On the way back to reception, Simon passed the break room. He stopped to speak to a colleague and placed the plant on the sunny windowsill for a moment. The colleague asked whether he had watered it recently. He said there was a team responsible for that. She asked which team. He considered this a very useful question, although it was not part of the current review cycle.
She touched the soil, brought a small amount of water, and suggested leaving the plant there for a while. Simon agreed, provided somebody informed reception. He sent a message saying the plant would be working temporarily from a different location.
Three weeks later, it had new leaves.
At the next managers’ meeting, Simon shared the result as an example of what could happen when expectations were made clear. He was particularly pleased that the plant had responded so well to feedback. The colleague who had asked about the watering looked toward the break-room windowsill. She had been checking the soil every Monday and Thursday. Simon had not put that in the case study.

