2026 Mid-Year Performance Appraisal

This year, I've built a tracking system that does two things: it gives operations the detailed visibility we need to fix problems, and it gives sales a simplified view so they can manage client expectations without getting overwhelmed by logistics detail. That's the key insight here — one system, two different interfaces depending on who needs to use it. For Operations (the detailed view): We now track every material from approval through installation. When something gets delayed, we can trace it back to the exact cause — was it the vendor shipping late, the warehouse processing slow, or a crew scheduling issue? This pattern recognition helps us solve the real bottlenecks instead of just reacting to problems. For Sales (the simplified view): We give them three critical milestones: when something shipped, when it arrived and was processed, and the estimated installation date. That's all they need to update clients. We learned that giving sales too much operational detail actually makes them anxious — they start calling about problems they can't solve, or they micro-manage logistics. The simplified version lets them do their job without that noise. The practical result: Operations can now see patterns (e.g., Vendor X consistently ships late, Warehouse is always backed up on Mondays). We can address these patterns proactively instead of scrambling when they impact crews. And sales can confidently tell clients timelines without creating false panic. This system also created two reports — one for ops with all the granular detail, one for sales with only what matters for client management. That separation of concern is exactly what we needed.

Greatest Achievement: Building a system that recognizes a fundamental truth — different teams need different information. Operations needs the nitty-gritty details to fix problems. Sales needs just enough information to manage clients. Throwing all the operational detail at sales creates panic, not productivity. So I designed two interfaces to the same data. This isn't just a tracking system; it's a strategic approach to how information flows through our company. What makes this an achievement isn't the technology. It's the thinking behind it. I had to understand what each team actually needs, what information would help them, and what would just stress them out. That required knowing both operations and the sales side well enough to design for both. Greatest Challenge: My instinct is to write things down and think deeply before I speak about them. I get nervous presenting to leadership because in a live meeting, there's pressure to answer on the spot, and I sometimes stumble. But I'm starting to see that this is actually a strength — the writing forces me to think clearly, organize my logic, and anticipate questions. So the real challenge is managing the anxiety around presenting while trusting that the preparation I do is solid.

Clear data entry guidelines so that the tracking stays consistent. When everyone logs information at different times and in different ways, the system is only as good as the messiest data point. Training with sales on what the simplified reports mean and how to use them. They need to understand that the three milestones (shipped, processed, estimated installation) are the only ones that matter for talking to clients. And honestly, confidence in presenting to leadership. I prepare thoroughly when I have time to write and think. But I'd benefit from having a few practice conversations with you before presenting something important, so I can work through the nervousness and know my logic is sound before I'm in front of the room.

Stop reacting and start predicting. The data already shows us which vendors ship late and when the warehouse gets backed up. I should be using that information to flag issues before they impact crews, not waiting for crews to call with a problem. Be more strategic about which data matters to which stakeholder. Not every data point needs to go to every audience. Sales doesn't need to know the warehouse was slow on Tuesday; they just need to know when the material will be ready for installation. Operations needs both. This strategic filtering makes the system actually useful instead of overwhelming. Build confidence in presenting. I've done the hard work of thinking this through and designing something that works. Now I need to trust that thinking and present it clearly without second-guessing myself.

The original goal was tracking and visibility, which I've achieved. But the bigger opportunity now is: "Design and implement stakeholder-specific reporting to improve both operational efficiency and sales accuracy." In other words, it's not just about collecting data. It's about delivering the right data to the right people in a way that helps them make better decisions. That's more strategic than the original MBO, and it's what I've actually built.

I've learned that being thoughtful and taking time to prepare is valuable, even if it means I sometimes appear quiet or uncertain in the moment. The conversations I've had with you about the tracking system — where we talked through how sales would react, how to present data without creating panic, what information each team actually needs — those conversations proved that this system works because we're thinking strategically, not just operationally. The system is live. Operations and sales are using it daily. The data we're collecting now will help leadership make better decisions about timelines, vendor relationships, and resource allocation. I'm ready to present this to the full team or to help replicate this approach in other parts of the business. And I'm committed to getting better at presenting these ideas clearly, because I believe the thinking behind this system is solid.