Case #002 - Asking for feedback

This ties into my blog about case #001. About a week after the interview, the person wanted to check in with the employer because there's an upcoming overseas trip with no internet access.

The Request

I had two days to pick from to boost the chances of getting good feedback from the interviews and, fingers crossed, an offer. We looked at the dates and picked the best one.

The Dates

Both dates were pretty good for career stuff, but one was definitely better! We planned to use one to ask for feedback from the potential employer and the other for internal career activities. Once we picked the dates, we stuck to their purposes. It felt like a game, assigning resources to get the best outcome. Date A was for internal career stuff, happening before Date B. Date B was for getting feedback from the potential employer.

What Happened - Date A

Date A went smoothly. Nothing unusual happened. The internal engagement was great and ended on a high note. Now, we're looking forward to Date B.

What Happened - Date B

On Date B, I texted the person, wished them luck, and helped maximize their chances. The meeting was in the morning, and judging by the chart, I was sure the response would be very positive.

Soon after, we got great news. The company decided to make an offer and started a conversation about the final compensation.

Conclusion

I was thrilled with the positive outcome and the offer. Analyzing the chart daily over time takes effort, but I'm glad we got the result we wanted. In this case, zwds helped us pick the best date for getting an offer.

I'm also sure this wouldn't have been possible if the person hadn't prepared and just waited for things to happen. It takes two to tango, and for zwds to be useful, the chart holder needs to put in effort to achieve what they want.

So, when zwds is used well, it maximizes benefits and minimizes harm. It's similar to what our ancestors called - 趨吉避兇