Someone at work wrote an eamil about me, but didn't send it to me. I am glad someone else forwarded me the email.

1.
Someone wrote an email at work
about me ....

2.
...but they didn’t send it to me.

3.
Someone else forwarded me the
email.

4.
This is what it said...
I've had the opportunity and pleasure of
working with Mike Foley
for several years now in my role as JON
Program Manager and Mike's
corresponding role as JON QE lead. During
that time Mike's continued
initiative, creativity, diplomacy and leadership
have been evident.

5.
Some quick examples:
-- Growing his team, and mentoring
individual's growth within that team.
He consistently gives his team members
"starring roles" in cross-team
efforts. He is diligient about giving credit
where due.

6.
-- Growing infrastructure/automation and
sharing across teams. Mike oversaw
the procurement and deployment of a
bladecenter, architecting a Chef framework
for multiplatform testing, and shared this out
with other QE teams when opportunities
arose. He's also been very involved with
docker images for JON testing.

7.
-- Excellent communication skills, as
evidenced by his weekly PM call
participation,
QE team reports, issue-oriented emails, etc.
I'd also refer to any of his Root Cause
Analysis (RCA) meetings as text book
examples of having meaningful, data-driven
discussions in a manner that does not put
anyone on the defensive.

8.
--Cross-team encouragement: Working with
Dev to institute feature completeness
demonstrations. This has been a huge win for
JON, and would be a great practice
for other teams to emulate.-

9.
-Cross-functional leadership: When I joined
the team years ago, Mike was leading the
bugzilla triage sessions, simply because it
needed to be done. In recent times he has
taken the initiative to schedule and lead
release retrospectives. In my experience,
neither of these are traditionally QE lead
responsibilities. He did a great job on all of
them.

10.
--Cross product leaderhip: JON Plugins have
historically been a very tough domain wrt
cross-product testing and inter-release
coodination. Along with GSS lead Larry
O'Leary and productization engineer Simeon
Pinder, Mike was instrumental in setting up
training and enablement for the managed
product teams. He has also encouraged
plug-in testingautomation, and helped to
enable it where possible. In particular, the
JDG team has praised the support received
from Mike's team on this front.

11.
--His inherent sense of priority is spot on. The
issues he highlights with the team do,
in fact, turn out to be the most important
issues at hand. He keeps them on the team
radar in a diplomatic but persistent fashion.

12.
-I’ve been significantly impressed by Mike's
productivity, vision, diplomacy and
leadership!
Regards,
Mark