Mentoring in Engineering and Computer Science

Work to balance the diversity of Participants in terms of demographics, professional area, and geographic location.

The context of the Engineering community is key here. It bounds the SEED program and defines its organizational character. Compare this to the Mentoring@Sun program, started in 1992 as a general Sun-wide mentoring program. The SEED program was developed by Sun in 2001 to address Engineering organization needs that were not met by Mentoring@Sun. That is, SEED is an internal mentoring and leadership growth program designed to meet the needs of a key professional area, running in parallel with a more general internal program.

  • Both SEED and Mentoring@Sun are very effective at making connections between organizational silos, what Helen calls cross-pollinating.
    For more on this, read my blog entry Internal or External Mentoring Program? (30 June 2009).Scope:
    SEED mentors can be from any part of Sun so long as they are at principal-level or above in seniority. SEED mentees, however, must all be working in Engineering, which is defined as:

    “Hardware and software engineering positions where the primary job purpose is to perform engineering research, design, and development activities resulting in innovative Sun products for external customers. Also included are staff positions providing strategic support to engineering research, design, and development activities.”

    Again, the Engineering professional context provides specific program boundaries: only these positions are included, others are not. (This would sound like inappropriate exclusivity if Engineering did not make up about half of Sun’s employees.)

    Training Focus:
    Each mentoring program should provide training that helps the pairs feel comfortable from the start and work well together for the entire term. Training is particularly important in special cases, such as when mentor and mentee work in different professional areas (Microelectronics and Finance, for example), have a wide gap in their relative experience or seniority (such as a Senior Director mentoring a recent college hire Member of the Technical Staff), are working at a distance (for over half of SEED mentoring pairs, the mentor and mentee work in different cities, states, or countries), or come from very different cultures.SEED offers two hours of individual training by phone for each mentoring pair. Using a standard set of materials (Helen and I update these annually), pair training is tailored to their strengths and challenge areas. The geek personality is common enough that our mentoring training materials have a special section for Engineering. Engineers are professional problem solvers who are usually very smart analytical logical thinkers. Sometimes it can be a stretch for them to see the other person’s point of view. Many of them do not suffer fools. Mentoring training for extreme geeks may focus on teaching how to disagree agreeably (using tactful phrases) and learning when problem solving may not be what is needed or wanted by their mentoring partner.

    Management Style:
    Managing an Engineering mentoring program requires communicating well and maintaining trust with Engineers. SEED is a prestigious leadership grooming program, so the decision of which applicants get accepted can be controversial. The selection system must be fair and seen to be fair. Selection criteria for SEED are based on the values of the Engineering community (such as: demonstrated technical excellence, creativity, leadership, holding patents, publishing papers, earning an excellent letter of recommendation by an executive, etc.) Many of SEED’s selection criteria are also reflected in job promotion criteria for Engineering staff. Sun Engineering has an egalitarian open door culture which values data-driven decisions and a transparent management style. While respecting confidentiality, SEED routinely makes a great deal of program information available to Sun Engineering. SEED program participants regularly contribute suggestions on how to improve the program and its web tools.

    What is the Geek Personality?

    A brief digression into the personal and social context of Engineers since this has such a strong influence on mentoring in Engineering…

    While Sun Engineering staff include a very broad range of personality types, there are some unusual concentrations. SEED mentoring training includes a section on Myers-Briggs style personality types. This provides a good context and vocabulary for mentoring pairs to discuss differences and commonalities and promote mutual understanding. (We skip this section of training for staff who think the use of personality types is Psychology black magic.) Sun used to offer personality assessments as part of its regular career coaching benefit. In 2002, I used a survey to collect information from 143 Sun Engineering staff about their formally assessed personality type. While not a statistically valid sample, it is nonetheless interesting:

  • 59% of the Sun Engineering staff reported that they had been assessed as I
    (introvert)About 50% of the US population are I (introvert)
  • 66% of the Sun Engineering staff reported that they were NT (intuitive thinkers)About 10% of the US population are NT (intuitive thinkers)

(Yes, this does mean that Engineers are abnormal, statistically at least).

Introverts have been defined as “people who find other people tiring” (see “Caring for Your Introvert” by Jonathan Rauch, The Atlantic, March 2003). A t-shirt popular with Engineers says “You read my t-shirt. That’s enough social interaction for one day.” (see Think Geek T-shirt). SEED works hard to make its communications comfortable for an introverted group. For example, we lay out the expected interactions and always allow the participants to engage at their own comfort level. One analysis of downside to being an introvert is that:

      “In our extrovertist society, being outgoing is considered normal and therefore desirable, a mark of happiness, confidence, leadership. Extroverts are seen as bighearted, vibrant, warm, empathic. ‘People person’ is a compliment. Introverts are described with words like ‘guarded,’ ‘loner,’ ‘reserved,’ ‘taciturn,’ ‘self-contained, private’ – narrow, ungenerous words, words that suggest emotional parsimony and smallness of personality. Female introverts, I suspect, must suffer especially. In certain circles, particularly in the Midwest, a man can still sometimes get away with being what they used to call a strong and silent type; introverted women, lacking that alternative, are even more

 

    likely than men to be perceived as timid, withdrawn, haughty.”(Ibid, 2003 article by Jonathan Rauch)

For more on Social Context, Gender, and Mentoring, see my blog entry Picking Your Mentor, Picking Your Mentee.

Finding Mentors for Engineering

Since 2001, I have matched almost 1,200 mentoring pairs; 70% of the mentors were executives (Directors, Vice Presidents, Principal Engineers, Fellows, etc.). SEED gets an average of 90% participant satisfaction rating on its quarterly reports, year after year. What do these executive mentors look for in mentees? Why do so many find SEED to be such a satisfying program? Most of the questions mentors ask when I contact them about working with a potential mentee are structural: availability, time commitment required to participate, potential areas of difficulty (like being in the same management chain or speaking different primary languages), and physical or time zone proximity are common questions. Along with those are asked more substantive questions about intellectual common ground, interests, and personal compatibility. Somewhere in this mix, almost all potential mentors ask something like “Why me? What does this person want to know that I am uniquely able to teach?” (For more on mentor questions and preferences, read my 6 July 2009 blog entry Picking Your Mentor, Picking Your Mentee).

Notice that relatively few questions are about the topic or professional area to be discussed. SEED Mentors have served from all areas of Engineering worldwide, plus Operations, Sales, Service, Legal, Information Technology, Finance, Human Resources, and Marketing. Most of the non-Engineering staff were recruited as SEED mentors at the specific request of a mentee who asked to learn from them. I originally recruited the General Counsel as a mentor because a Software Engineer wanted to learn more from the lawyer’s success as a business leader. (He enjoyed the experience and has served as a mentor five times since.) I recruited a Finance Vice President because a Systems Program Manager wanted a mentor who really understood financial planning, revenue and cost management. Sun Microsystems is an Engineering-driven company, so most non-Engineering staff are eager to help (as well as extend their own connections in Engineering).

I have observed that the more experienced or senior a mentor is, the more willing they are to discuss a very broad range of topics. It is usually the more junior mentors who question their breadth of ability or the value of their experience outside of their immediate area of professional expertise. The mentors who seem to get the most out of their SEED experience are the executives. One Software Vice President told me that his hour with his mentee was his vacation, the only time all week when he knew the answers. A different Software Vice President told Helen that he always looked forward to meeting with his mentee: it was his only non-confrontational meeting. This positive experience is reflected in SEED’s metrics for repeat mentor participation:

  • 48% of the total 460+ potential mentors on SEED’s current list have been mentors more than once. This includes principal-level senior staff
    plus executives.(This does not count their service in Mentoring@Sun or other Sun mentoring programs.)
  • 65% of those repeat mentors are executives.
  • 54% of all of the executives who have ever been SEED mentors have mentored more than once.45 executives have have served as a SEED mentor five or more times.4 Sun executives have mentored ten or more times with SEED.

A Marketing Vice President wrote in evaluation of his sixth SEED mentoring experience:

“This continues to be a great program and I get a lot out of it — possibly more than the mentees.”

Series

Information is from my experience since 2001 managing Sun’s SEED Engineering-wide world-wide mentoring program, and from the Mentoring@Sun general mentoring program, and the mentoring program for new Sun Vice Presidents managed by Helen Gracon since 1996. Helen Gracon also provides training for SEED. This is part of a continuing series on mentoring programs. Other entries in this series:

For more about SEED, see the program home page at http://research.sun.com/SEED.

By Katy Dickinson
Director, Business Process Architecture
Chief Technologist’s Office & Sun Labs, Sun Microsystems

1 Comment

Filed under Mentoring & Other Business

Mentoring Program Web Tools and Process

Web tool design is a technical art which requires an unusual combination of software programming, usability engineering, and program management skills. As Director of Sun Microsystems’ SEED Engineering-wide worldwide mentoring program since 2001 (and the program’s Process Architect), I have been gifted with two talented staff members who can do this work. Tanya Jankot has been SEED’s Applications Engineer since 2003. Before Tanya  Justin Yang held the position of SEED Program Manager for two years.

SEED developed its own set of tools for mentoring program and information management. These tools have not been “productized”. Why not use an external-to-Sun set of web tools? For the answer, read my 30 June 2009 blog Internal or External Mentoring Program?

Tools and Process Overview

The original SEED program was based on a year-long need analysis and program design in 2000 by a team mostly made up of Sun Human Resources (HR) and Engineering staff. The process itself was created on-the-fly during the first pilot term in 2001. The SEED mentoring program has expanded to a much larger audience in recent years and SEED’s web tools have developed and been redesigned accordingly. In the program’s first year, 2001-2002, there was just one term. In 2008-2009, there have been 12 overlapping terms in four groups (Recent Hires, Established Staff, PreSEED, and special pilots). Since the SEED team and I were creating a new mentoring system essentially from scratch in the 2001 pilot term, our guidelines for process and tool development were:

  1. Keep it simple
  2. Check in with customers and stakeholders frequently
  3. Only include the minimum: question the need for each step before it goes in, and again at every review, and again before publication
  4. Let the process define the web tools
  5. Assume that process and tool users will have access to only the most basic web resources and performance
  6. Collect and analyze data routinely and make decisions based on those data

These guidelines have continued to serve SEED well. We also kept using the concept of a “pilot” to expand the program. In pilot terms, the rules, process, and/or scope are somewhat different from the regular SEED program. The Established Staff group was created in 2002 and the PreSEED program was created in 2008 using pilot programs; both have been very popular offerings. A pilot allows us to put something imperfect out there to see
what works. Sometimes pilots fail (for example, the SEED-2 or SEED Alumni term in 2007 only attracted ten participants).

SEED now has two major formal processes, for participant selection, and for mentor selection. These processes are published in full detail for the use of Sun internal program participants. Flow charts are also available in the appendix of “Sun Mentoring: 1996-2009” the Sun Labs 2009 Technical Report  (includes a copy of the Research Disclosure Database Number 482013, defensive publication from Research Disclosure, Published in June 2004, Electronic Publication Date : 17 May 2004).

In November 2008, Tanya created and gave an internal-to-Sun presentation on developing simple web technologies using the SEED tools as examples. Her presentation was created to educate other Sun project teams and web teams. The information following about SEED web tools is derived from Tanya’s presentation. Her overview statements about the SEED’s current web tools:

  • The technology was built to model SEED mentoring processes which were already designed and pilot tested (we tried to fit the tools into the existing work flow rather than build processes around the tools).
  • The tools have evolved with the program: need for greater automation to allow scaling, new requirements as the program expanded across geographical areas regions, organizations, etc.
  • SEED relies on existing Sun corporate data systems as much as possible, only
    gathering additional information not already available elsewhere.

More specific details follow about SEED’s web tools and the technology and process behind them. Screen shots and other confidential data have been removed from Tanya’s original presentation material.


Developing Simple Web Technologies for the SEED Mentoring Program

Tools Behind the Program

  • The systems supporting the SEED program have evolved with it over time. They currently include:
    – A system to manage each term’s application process. Details are in Term Application Materials and Term Application Management, below.
    – A system to support the mentor matching process. Details are in Mentor Request Management, below.
    – An archive of program applicants, participants, mentors, etc. which enables long-term program management and metrics. Details are in
    SEED Program Database, below.
    – Applications to support regular program activities, such as regular quarterly feedback reports and bi-annual events for mentees, mentors, and the mentee’s managers.
  • Tool development goals:
    – Ensure the integrity and confidentiality of applicant and participant data.
    – Increase the ease-of-use for program participants and SEED staff.
    – Increase program efficiency and quality of data available to the SEED team, extend the number of participants, raise the value of participant experience, and justify their trust in the program

Simple Technologies

  • “SAMP” (Solaris, Apache, MySQL, and Perl & PHP)
  • htaccess and Sun confidential employee records access authentication
  • Queries to the Sun confidential employee records system
  • Email
  • Other technologies available within Sun and Sun Labs, such as a name auto-suggest widget and a survey tool.
  • And still making use of old-fashioned static web pages

Term Application Materials

  • SEED terms have an application period, usually lasting two to three weeks, with firm deadlines.
  • htaccess and Sun confidential employee records access are used for authentication
  • In addition to submitting a completed application form, applicants must also submit their resume, their manager must submit a letter of recommendation, and in some cases they must also secure additional letters of recommendation from Sun executives. All materials are submitted through web-based forms.
  • Design considerations
    – Applicants are located worldwide.
    — Application materials need to be as clear and simple as possible because for many employees, English is not their primary language.
    — Applications must be functional on all Sun systems and locations. This includes Sun hardware with Solaris software, Sun Ray systems, experimental systems, as well as a variety of Macs, laptops, and PCs.
    – Application materials must reflect Sun’s organizational structure and HR policies in an understandable way. Many applicants are new to Sun and are not familiar with its organization or policies.
    — Divisions, organizations
    — Job Codes, titles
    – Manager and executive recommendation letters are submitted confidentially but are a required part of an application. A secure mechanism is needed for applicants to view the status of their application but not the details of all materials.
    – In order to ensure that all materials are submitted correctly and not “lost” (i.e., a recommendation letter is submitted against an incorrect applicant SunID), Sun confidential employee records system lookup, email confirmations, and SQL audits of the database are used.
    – Each term’s application materials are stored in a separate database for easy management. Key applicant data that needs to be tracked long-term is loaded into the SEED archive database at the end of the application period.

Term Application Management (SEED Team Website)

  • A central website used by the SEED program staff to efficiently track the status of applicants and their materials.
  • At the end of the term application period, key applicant data is verified against Sun’s Human Resources records.
  • Used by SEED’s executive selection committee to review each applicant thoroughly.
  • Tool goals
    – Present useful summary data in a small amount of space.
    – Accurately reflect the status and materials received for each applicant.
    – Allow a complete review of each applicant’s submitted materials.
    – Make information easy to find to answer questions from applicants, participants, managers, and mentors quickly and accurately.
    – Print in a useable format.

Mentor Request Management

  • Upon acceptance to the program, all participants are required to submit a 10-name “Mentor Wish List” of mentors they would like to work with.
  • At the close of the mentor request period and receipt of all wish lists, the SEED program staff begins the mentor match process. For each participant, the goal is to match them with the highest priority eligible mentor from their Mentor Wish List.
  • A decision is made in each case where more than one Participant requests the same potential mentor. In SEED’s current terms, 80 mentees prepared 10-name lists, which resulted in 387 unique mentor requests. There were 10 potential mentors with multiple 1st Priority requests and 39 mentors who were requested by 5 or more mentees. This is a common problem: as many as twenty-two(!) potential mentees in one term have requested the same mentor. The primary basis for this decision is the priority order on the Mentor Wish List provided by the Participant. The Participant’s seniority (number of years at Sun) may be used as a tiebreaker, with the more senior Participant getting preference.
  • Tool Requirements
    – For each mentor requested, both name and SunID are required to be entered due to variations in name entry and frequent errors in entering SunIDs.
    – A name auto-suggest widget has been very useful in creating cleaner submissions.
    – The Mentor Request form includes a validation step in order to check for known conflicts in the SEED Potential Mentors list.

SEED Program Database

  • The SEED program database drives the long-term management of the program.
  • It allows us to track past applicants, participants, and mentors, as well as manage our list of 450+ Potential Mentors: mentors who have volunteered to work with program participants.
  • These records allow for regular metrics analysis of the program, currently done annually. Automated metrics tracking is a goal that is in progress.
  • Challenges
    – Maintaining the data so it is meaningful over time. For example, divisional organizational changes (reorg) make it difficult to summarize the number of participants we have had from each organization over the life of the program.
    – Keeping the mentor records up-to-date: removing broken links, updating titles in a timely way.
    – We need to maintain records of all program mentors, participants, and applicants, even after they have left Sun.

Conclusions

  • The systems and tools that support SEED have evolved with the program over time. They are not a single unified system, but being modular are easy to modify or extend when changes are required.
  • Using the technologies that are available and used by others allows you to be more efficient: learning from their work, and sharing components when possible.

Series

This is part of a continuing series on mentoring programs. Information is to answer frequently asked questions, based on my experience since 2001 managing Sun’s SEED Engineering-wide world-wide mentoring program. Other entries in this series were integrated into “Sun Mentoring: 1996-2009” the Sun Labs 2009 Technical Report.

25 October 2013 – links and text updated

Leave a comment

Filed under Mentoring & Other Business

Cactus Valentine

About six months ago, my husband,   John Plocher carved me a cactus valentine. He got the idea from a cactus we saw at Poot’s House of Cactus in Ripon, California. Our carved cactus is one of the many huge prickly pear Opuntia or nopales paddle cactuses in our yard. Before our neighborhood of houses was built in Willow Glen, local historians tell us that there was a chicken farm and a prickly pear cactus farm on the land.

John says he was inspired to take a knife to the cactus by it poking him one too many times while he was working in the garage. I admit I did not notice
his creation until he pointed it out but it makes a funny addition and does not bother the cactus.

carved prickly pear cactus, san jose california<br /> photo: copyright 2009 Katy Dickinson carved prickly pear cactus, san jose california<br /> photo: copyright 2009 Katy Dickinson

Images Copyright 2009 Katy Dickinson

Leave a comment

Filed under Home & Family

Picking Your Mentor, Picking Your Mentee

Information in this entry is taken from my experience since 2001 managing Sun’s SEED Engineering-wide world-wide mentoring program. This is part of a continuing series on mentoring programs, answering some of the questions I am most frequently asked. Other entries in this series:

Using a Formal, Structured Approach

This entry speaks to would-be-mentees as well as to potential mentors on how to pick their mentoring partner. Both are addressed here so mentor and mentee can see the whole picture. Specific mentor matching systems are covered in Mentor Selection Systems. In general, I recommend a formal, structured approach like that we use in the SEED program, because I have seen this approach work in almost 1,200 matches, 70% of which were with an executive mentor. You can learn more about SEED by reading the blog entries listed above. Also, flow charts of how SEED’s process works are available at “SEED: Sun engineering enrichment & development” Research Disclosure Database Number 482013, defensive publication in Research Disclosure, Published in June 2004, Electronic Publication Date : 17 May 2004 (5 pages, PDF format).

Doris Lessing at lit.cologne 2006, from Wikipedia “That is what learning is. 

You suddenly understand something you’ve understood all your life,

but in a new way.”

– Doris Lessing (2007 Nobel Prize in Literature, 1919-now)

For the Mentee: Start with a Mentor Wish List and Learning Goals

Before the mentor matching cycle starts, each SEED mentee is asked to prepare a 10 name Mentor Wish List which is prioritized and includes a reason why the mentee would prefer to work with each mentor included. Three learning goals are also part of the SEED Mentor Wish List.

  • Why 10 names?
    I have run mentoring terms in which we asked for 5 names but it wasn’t enough: I ended up going back to the mentee for more potential mentor names too many times. I have also run terms in which we asked mentees for 15 names but since each name represents serious thought
    and research and we very rarely ended up needing all 15, we cut it down. In practice, 10 potential mentor names seems the right number. In the current group I am matching of 80 mentees (just 14 still unmatched), I have only had to go back to 2 so far for additional names.
  • Why prioritize potential mentors?
    • First, to get the mentee-to-be to think seriously about who they want their mentor to be by forcing a ranked comparison. It takes time and mature consideration to work through all of this. Creating the Mentor Wish List is probably the hardest part of the SEED program; however,
      that advance thinking contributes to a more successful mentoring partnership.
    • Second, to help the program staff decide when there are duplicate requests for the same mentor. In SEED’s current terms, 80 mentees prepared 10-name lists, which resulted in 387 unique mentor requests. There were 10 potential mentors with multiple 1st Priority requests and 39 mentors who were requested by 5 or more mentees. When a mentor is requested by more than one mentee, SEED’s primary basis for picking one mentee over the other is the priority order. The mentee’s seniority (number of years at Sun) may be used as a tiebreaker, with the
      more senior mentee getting preference.
  • Why require mentees to write reasons for preference?
    This is to answer the #1 question asked by potential mentors: “Why me? What does this person want to know that I am uniquely able to teach?” That is, before they make any decision, potential mentors (especially executives whose time is particularly valuable) want to gauge the mentee’s motivation and seriousness. They want to see if spending six months with this mentee is a good use of time. SEED sends each potential mentor an email including the potential mentee’s resume, 3 learning goals, plus reasons for preference. We offer additional information (the application form and letters of recommendation) but most matches are made based on the first email plus a pre-match conversation between the potential mentor and potential mentee. Very often, the potential mentee’s own words in their preference statement makes the match. Some mentees think to save time by providing the same reason for preference for all of their potential mentors. Mentor Wish Lists are returned for revision when this happens. Reasons for preference should be as unique as the mentors themselves.
  • Why require learning goals?
    The mentee’s three learning goals give the potential mentor an idea of initial topics for discussion (where their conversations will begin). This helps the potential mentor evaluate whether they can help the mentee. The SEED Engineering mentoring program takes a long-term view and does not have a preference for one kind of learning over another. That is, the mentoring partnership learning does not have to have anything to do with the mentee’s current job. Some people want to learn to be better technical managers, others want to know how to get their ideas to customers faster. Many want to improve their soft skills: public presentation or speaking, negotiating, conflict management, and coaching. Still others want to improve their work and family balance and still have a great career. More general and broader learning goals usually work better than specific or very technical goals. Extremely specific goals or requests to work on a particular project with the mentor often discourage even the most accomplished mentor and make the mentee very difficult to match. Three examples of 3 broad learning goals: 

    1. Learn more about how to lead a virtual team.
    2. Learn how to communicate with my management team.
    3. Learn how to communicate better with customers.1. To be engaged intellectually with senior peers.
    2. To apply my analytical skills and interests to a new and interesting area.
    3. To increase my own motivation.

    1. Diversify my knowledge by learning from individuals in other business units at Sun.
    2. How to take on more responsibility and enhance my visibility at Sun.
    3. Improve my understanding of corporate expectations from a technical leader and improve my leadership skills.

For the Mentee: Who Goes on Your Mentor List?

Potential Mentors should be included on a Mentor Wish List primarily because of their accomplishments, experience, personality, capabilities, or skills. For
more on this “Demonstrated Accomplishment” selection system, see

Mentor Selection Systems
.

The Cheshire cat as John Tenniel envisioned it in 1866, from Wikipedia Alice: “Would you tell me, please, which way I ought to go from here?” 

“That depends a good deal on where you want to get to,” said the Cat.

“I don’t much care where -” said Alice.

“Then it doesn’t matter which way you go,” said the Cat.

Alice in Wonderland, 1865, by Lewis Carroll

The focus of mentoring in the SEED program is long-term professional and technical development. It is not appropriate for a mentee to request a mentor with the sole aim of being hired into a specific job, securing project funding, or gaining a particular political advantage.

Social Context, Gender, and Mentoring

In addition to Demonstrated Accomplishments, many mentees seek a mentor who shares their social or personal context in terms of gender, race, ethnicity, shared language, nationality, or other demographics. These characteristics may properly be part of why a particular mentor is requested; however, in my experience these characteristics by themselves do not provide enough commonality for six months of discussions, so no one of them will be successful as the sole reason for preference. When SEED receives a Mentor Wish List containing inappropriately simplistic reasons for preference like “He is a very successful Chinese in Sun” or “Female Mentor in a top role in an organization”, that list is returned to the potential mentee for expansion.

However, these social and personal characteristics can be very important in professional life and are appropriate topics for some mentor-mentee discussions. Gender in particular may have an influence on how mentors and mentees respond to mentoring programs. Women and non-US staff have taken advantage of the SEED program at a consistently higher rate than their representation in Engineering overall. The Anita Borg Institute for Women and Technology and the Michelle R. Clayman Institute for Gender Research, Stanford University, prepared an excellent study in 2008 called Climbing the Technical Ladder: Obstacles and Solutions for Mid-Level Women in Technology (by Caroline Simard, Andrea Davies Henderson, Shannon K. Gilmartin,
Londa Schiebinger, and Telle Whitney) which reported:

    “Women at the mid level are more likely to rate the availability of mentors and mentoring programs as important to retention than are men (48.7% versus 36.2%). (The gender difference on this item is especially wide at the entry level, where 60.6% of technical women point to a need for to mentoring programs, compared to 39.1% of men.)”

As reported in SEED’s “5 Years of Mentoring by the Numbers” (by Katy Dickinson, presented at the October 2006 Grace Hopper Celebration of Women and Computing, 30 pages, PDF format), based on SEED’s data since 2001, there are three consistent gender patterns with regard to mentor matching in Sun Engineering:

  • More male mentors are requested by both male and female mentees overall.
  • Female mentors seem more willing than male mentors to accept a mentee, regardless of gender.
  • Female mentees request twice as many female mentors on their Mentor Wish Lists as do male mentees.

Some questions this has raised:

  • “Is there a substantive difference in reported satisfaction between mentees with male mentors and those with female mentors?”One of the opinions (often a seemingly-unquestioned assumption) I often hear from managers of other mentoring programs is that women exclusively want and benefit from having mentors who are also women. While the SEED Engineering mentoring program’s data show that female mentees have a strong preference for female mentors, it also shows that men and women mentees report the same program satisfaction
    (90% average), regardless of their mentor’s gender. That is, SEED’s data over many years show that there is no real difference in reported satisfaction. The sample size of female mentees is smaller than the sample of males (this is Engineering, after all); however, there is no pattern of satisfaction difference.
  • “What is the downside to special mentoring programs for women?”As Dr. Ellen Spertus wrote in “Why are There so Few Female Computer Scientists?” (MIT AI lab Technical Report 1315, August 1991):”While there is a need for affirmative action programs, they have large negative effects that must be considered. Even if a program does not entail lower standards for women, doubts are cast on a woman’s qualifications in a society that already mistrusts them. Programs with lower qualifications may be a tactical mistake (in addition to being unjust) because people may be put in situations for which they are not qualified, giving them less overall success and self-confidence than they would have had otherwise. These negative effects should be weighed when considering implementing an affirmative action program.”

For the Mentee: Researching Potential Mentors

A good background search by the mentee will result in more detail and understanding of the potential mentor, also resulting in a more convincing reason for preference. Many times, the mentee’s explanation convinces the potential mentor to consider them seriously. Sometimes, it makes the match. Mentees should not confuse researching mentors with asking someone to be their mentor: these are two different steps.

Mentor Research Steps:

  1. The mentee should start by thinking about mentoring relationships she has already had (personal, academic, or professional) and ask herself:
    What would I do the same or differently? Do I want a mentor who is similar or different? She should also think about what she wants to learn from another mentoring relationship: what need or gap do she want to fill in her accomplishments, experience, personality, capabilities, or skills? Are there patterns of behavior or performance feedback to be considered?
  2. The mentee’s second step in researching potential mentors should be to ask her supervisor or manager for support and advice. The manager knows the mentee and has a professional stake in the mentee’s success. Also, the mentee should ask for advice from other people who know her well – taking advantage of their experience, wisdom, and networks.
  3. A general search for background on the potential mentor using a web search engine is the next step. In particular, the mentee should look for professional profiles on web communities such as LinkedIn or Plaxo (rather than the more social communities such as Facebook). Many Directors and Principal Engineers will have executive profiles prepared by their company. Most Vice Presidents will have such a page.
    The web home page of potential mentors’ professional or academic organizations may also be a fruitful source of information. Groups such as
    Association for Computing Machinery (ACM) and IEEE offer biographies of award winners, office holders, etc.
  4. In searching for mentors, it may help the mentee to go through a list of leaders or executives in her professional or academic area to pick out the people who have titles the mentee wants for herself someday. The mentee should pick out names of people who are already far down the career path in which she has an interest. This is like doing research for a university paper – hunting for leads, backtracking, looking for key words, hunting again. Mentees should expect to spend many hours developing a good Mentor Wish List.
  5. The mentee’s manager can provide perspective by checking the Wish List after it is complete, before the mentee goes into the mentor matching cycle.
Mohandas Karamchand Gandhi, pictured in the 1930s, from Wikipedia “Where the ultimate goal is the search of truth, 

no matter how a man’s plans are frustrated

the issue is never injurious and often better then anticipated.”

– Mahatma Gandhi (1869-1948)

For the Mentor: Deciding to Become a Mentor

Since the mentee drives the relationship, the mentor is usually in the position of deciding whether to accept a specific mentoring proposal, rather than having to seek out a mentee. Common questions from mentors include:

Why become a mentor?

  • One SEED mentor who had turned down several mentee requests wrote when he did accept someone: “I’ve been struggling with this however I’ve (finally) decided that I want to do it. I’ve asked other people for help along these lines so I guess it’s time for me to give a little back.”
  • A Vice President-Fellow mentor who had already served in several SEED terms wrote in his first email to his new mentoring partner: “I look forward to our mentor-mentee relationship. This will be a good experience for both of us. I will learn some and you will learn some, it is up to us to make the most out of it.”
  • A Distinguished Engineer wrote in his quarterly report: “This is a very worthwhile program that I’m pleased to be able to participate in. In the two times I’ve participated as a mentor I’ve gotten at least as much out of the experience as the mentee.”
  • A Vice President wrote in evaluation of his 6th SEED mentoring experience: “This continues to be a great program and I get a lot out of it — possibly more than the mentees.”
  • A Software Staff Engineer wrote about his 2nd SEED mentorship: “Love the SEED program. Low cost to shareholders, high value to
    shareholders.”
  • A Distinguished Engineer who is an 11-time mentor wrote: “SEED is a great opportunity for both Mentor and Mentee. It opens both
    personal and technical doors by providing a 1-1 context outside of normal work requirements.”
  • In addition to giving personal and professional satisfaction, becoming a mentor can help expand understanding and experience.
    Mentoring may also specifically support professional development in organizations where leadership is one of the criteria for evaluating promotion potential.

In their own words:

  • “What do mentors do?”
  • Working in parallel with the mentee’s manager (and communicating with the manager as appropriate while respecting confidentiality), the mentor recommends training and experiences, makes introductions, provides continuing advice, assistance and support, and evaluates progress. Some mentors may discuss or work together on projects with mentees. Mentors may also be asked to support the development of the mentee’s “soft” skills such as public presentation/speaking, negotiating, conflict management, and coaching.

  • “What do mentors look for in mentees?”
    The mentor should be interested in at least some of the same work areas, problems, or projects as the mentee. However, working in the same broad professional area (software, microelectronics, sales, etc.) may or may not be an advantage to a mentoring pair. There have been very successful mentoring partners who shared a technical focus but were in very different areas. Sometimes having a different specialty can be a real advantage because there is more to talk about and learn. Personal compatibility and commonality (with both the mentee and their manager with whom the mentor may need to communicate from time to time). Physical proximity or time zone proximity may or may not be important. Proximity may mean that the mentor and mentee have offices near each other or that one of them can travel for an in-person visit from time to time. However, while face-to-face meetings are valuable, they are not always possible. A great deal can be accomplished over the phone and by email. For many years, the majority of SEED mentor-mentee pairs have worked at a distance (in difference cities, states, or countries). In a global workforce, potential mentees may work in an area where there are few or no senior Engineering staff available to mentor them. In their case, being mentored “at a distance” is their only choice. 

    In their own words:

    • In April 2003, a mentor wrote in his quarterly report: “…the impact one can make by being a mentor in a non-US Geo is considerably high, as per my personal experience. I derived a lot of satisfaction and good perspective during this mentoring program. Also, this Mentoring program made me to think about some issues affecting the local engineering center, and we are working towards addressing these issues.”
    • In July 2009, a mentee working in Japan spontaneously wrote an evaluation of his relationship with his mentor (who works in Israel): “I cannot thank more for his effort he put into this program, his frankness and openness as well as shared knowledge not only regards to the professional life but also the personal life. … Though my goal was slightly different at the beginning of the term, learning from someone who is ahead in professional life, while managing his work-life balance provide me a new perspective. Managing balance is still challenging for me, but sharing simular experience about family from different point of view was and continue to be helpful for myself. Visiting the differences in each others’ culture starting from the calendar was, for me an exotic experience and continue to be interesting one. I am looking forward to continuing our relationship.”
  • Availability (if the mentor is a senior executive or a manager with a large staff, she will have less time).
    Potential conflicts of interest or areas of discomfort with the mentee or the mentee’s manager (for example, it may be a problem if the mentor and mentor are in the same management chain, or if there are close personal relationships). Mentor and mentee should talk about these potential conflict areas before being matched.

Common questions mentors report thinking about when deciding whether to accept a particular Mentee include:

  1. Why me? What does this person want to know that I am uniquely able to teach?
    Potential mentors (especially executives whose time is particularly valuable) want to gauge the mentee’s motivation and seriousness. They want to see if spending six months with this mentee is a good use of time.
  2. Do I already know the mentee who has requested me (or know of them, or know their manager)?
    That is, is there a prior connection or knowledge? The prior connection may allow the mentoring partnership to start sooner and at a deeper level, or the history between the mentor and mentee may slow or prohibit the development of a partnership. In any case, it needs to be thought through.
  3. Is there a line reporting relationship?
    It may be a problem if the mentor and mentor are in the same management chain.
  4. What is my availability during the mentoring term?
    Most mentors take mentoring very seriously and want to be sure they have the time to do a good job as a mentor. If the potential mentor has just taken a big new job or has irreducibly large personal or professional time commitments, she probably will not accept a mentee until her schedule is lighter.
  5. Can I effectively partner “at a distance”?
    Mentoring across distance and time zones may be a skill that the potential mentor needs to develop. SEED mentoring pairs who work at a distance have for many years report the same satisfaction level as those working locally; however, mentors and mentees both report that working at a distance is more time consuming.

Circumstances mentors have identified as being important when considering a mentee include a mix of:

  • Mentor’s availability when asked (almost always the #1 consideration)
  • How well the potential mentor’s and mentee’s schedules match (and their flexibility to accommodate  each other’s schedules)
  • Mentee’s accomplishments, experience, seniority
  • Mentee’s capabilities, skills, potential
  • Common intellectual or professional interests
  • Personal compatibility or common ground (including linguistic abilities: whether the mentor and mentee share a common language)
  • Physical, geographic, or time zone proximity
Senator John F. Kennedy in his Senate Office, 1959, from Wikipedia “Leadership and learning are indispensable to each other.” 

– John F. Kennedy (35th U.S. President, 1917-1963)

Photos are from Wikipedia

1 Comment

Filed under Mentoring & Other Business

Gar Skull

A year ago, my brother-in-law Marty accidentally ran over a surprising and large toothy gar with a speedboat on Loon Lake in Wisconsin. Gars are big non-native predators which we don’t want in our little lake killing the game fish, so no one was sad that it died. It is also not edible, so Marty threw it up onto the hill behind the cottage once I had taken a photo.

This summer, the kids found the skeleton of the gar on the hill and had fun checking it out. All of those sharp little teeth in the long jaw are creepy but very interesting.

Marty and the Gar, 2008

Marty Plocher and the Gar, Loon Lake Wisconsin<br /> photo: copyright 2008 Katy Dickinson

Gar Skull, 2009

Gar Skull, Loon Lake Wisconsin<br /> photo: copyright 2009 Katy Dickinson

Images Copyright 2008-2009 Katy Dickinson

Leave a comment

Filed under News & Reviews

Mentor Selection Systems

Information in this entry is taken from my experience since 2001 managing Sun’s SEED Engineering-wide world-wide mentoring program, and also from the Mentoring@Sun general mentoring program and new Vice President program managed by Helen Gracon. This is part of a continuing series on mentoring programs, answering some of the questions I am most frequently asked. Other entries in this series:

Mentor Selection Systems

I have seen four kinds of formal mentor selection systems:

  1. Mentee evaluates potential mentors’ Demonstrated Accomplishments, experience, personality, capabilities, and skills, then creates a prioritized list of preferred mentors (SEED calls this a “Mentor Wish List”). Mentoring program staff approaches mentors on behalf of mentees.
  2. Mentor and mentee each use Self-identified Competency lists to indicate strengths and weaknesses. Mentoring program matches based on list compatibility. Mentees are given two mentors to contact. Mentoring@Sun uses this system.
  3. A combination of the two options above.
  4. Assignment of mentors by management.

This entry will discuss formal systems using Self-identified Competency vesus those using Demonstrated Accomplishment for mentor selection.

Cognitive Bias

I am going to take a small detour to introduce the concept of cognitive bias, specifically the Dunning-Kruger effect humorously described by Justin Kruger and David Dunning, (then both of Cornell University) in their much-cited and entertaining paper “Unskilled and Unaware of It: How Difficulties in Recognizing One’s Own. Incompetence Lead to Inflated Self-Assessments.” (Journal of Personality and Social Psychology, 1999, Vol. 77, No.6. 1121-1134). Two findings from that paper which are pertinent to mentor selection are:

  • “the incompetent will tend to grossly overestimate their skills and abilities”
  • “participants in the top quartile tended to underestimate their ability and test performance relative to their peers”

Kruger and Dunning quote Charles Darwin (1871): “ignorance more frequently begets confidence than does knowledge.” That is, people are often bad at knowing what they are good at.

I recommend reading this paper not only to understand cognitive bias but also to enjoy passages such as:

  • “…knowledge about the domain does not necessarily translate into competence in the domain, one can become acutely — even painfully — aware of the limits of one’s ability. In golf, for instance, one can know all about the fine points of course management, club selection, and effective ‘swing thoughts,’ but one’s incompetence will become sorely obvious when, after watching one’s more able partner drive the ball 250 yards down the fairway, one proceeds to hit one’s own ball 150 yards down the fairway, 50 yards to the right, and onto the hood of that 1993 Ford Taurus.”
  • “In sum, we present this article as an exploration into why people tend to hold overly optimistic and miscalibrated views about themselves. …Although we feel we have done a competent job in making a strong case for this analysis, studying it empirically, and drawing out relevant implications, our thesis leaves us with one haunting worry that we cannot vanquish. That worry is that this article may contain faulty logic, methodological errors, or poor communication. Let us assure our readers that to the extent this article is imperfect, it is not a sin we have committed knowingly.”

Self-identified Competency Systems

Cognitive bias is important because most mentor selection systems rely on Self-identified Competency lists. In a Self-identified Competency System, mentors and mentees are presented with lists of competencies. Each picks competencies that they think they have. The system then proposes mentor-mentee pairings based on comparing list selections. (What I call a Self-identified Competency selection system, Peg Boyle Single and Carol Muller of MentorNet call “Bi-directional Matching”. See “When Email and Mentoring Unite” in Creating Mentoring and Coaching Programs from the ASTD In Action Series, by Phillips and Stomei, 2001.)

Competency lists vary widely depending on the context and goals of the mentoring program but examples include:

  • Negotiation
  • Customer Focus
  • Building Trust
  • Listening Effectively
  • Strategic Decision Making
  • Selling the Vision
  • Building Successful and Effective Dispersed Teams
  • Technology Impact Assessment
  • Working Across Cultures
  • Network Design and Architecture

Those using a Self-identified Competency Selection System should be aware of cognitive bias as it may get in the way of finding a good match. That is, both the mentee and potential mentor will probably not be objective in assessing strengths and weaknesses (competencies), so the match may be based on a false compatibility evaluation. However, the seemingly-objective way in which the match was made (how can you go wrong picking from a list?) may mask selection errors until they are demonstrated in experience, frustrating both mentor and mentee.

Punched metal mask by Paul Dickinson Goodman photo: copyright 2009 Katy Dickinson An inappropriate mentor selection system may mask errors.

Competency lists can be used to control the scope of learning in a mentoring program. So, if a Vice President wants to direct her organization to learn more about working with virtual or dispersed teams, she could pick a list of competencies which had to do with that skill area, thus encouraging mentor and mentee to discuss the desired topic. This may limit the scope of discussions (which can be good or bad, depending on what the program sponsor and participants are looking for). Controlling competency scope will also limit which mentors are considered (or available). Some mentees and mentors will find the preferred discussion topic too simplistic and may either break off their relationship or ignore the sponsor-preferred topic limitations.

When the competencies are specific to a particular job or profession, a Self-identified Competency Selection system works best when the mentor and mentee share a professional context and interpret the competency lists similarly. For example, if both mentor and mentee are in Information Technology Operations, they will understand the competency “Identity Services” to mean “experience with the design and implementation of a multi-level identity/authorization strategy” but someone in Marketing Communications would probably interpret “Identity Services” very differently. The professional context may also be one of seniority. If the mentor and mentee are both Vice Presidents, they are likely to share an interpretation at a higher organizational level, which is less likely if the mentor is a Vice President and the mentee is a junior Engineer. Shared context is less important when the competencies are soft skills, such as negotiating, public speaking, conflict management, etc.

Demonstrated Accomplishments and SEED

SEED is one example of a mentoring system which relies on Demonstrated Accomplishments for mentor selection. About 70% of SEED mentors are executives. A different mentoring program, run by Helen Gracon out of the Sun Learning Services group for new Sun Vice Presidents, also uses Demonstrated Accomplishments for mentor selection. Both programs are regularly given 90% or higher satisfaction ratings by participants.

The SEED program maintains a list of Potential SEED Mentors (over 450 now). The list includes the name, job title, division, and city/state/country of each potential mentor, plus links to biographical information such as SEED mentoring history and evaluation, personal web pages, blogs, executive profiles, LinkedIn profiles, resumes, etc.

The SEED program has an open list of potential mentors: any senior Sun Engineer or executive is eligible. SEED participants are not limited to the choices on the Potential SEED Mentors list. About a third of the mentors in most terms are new to SEED and were not originally on the Potential SEED Mentors list. The SEED program welcomes Mentors from both the business and technical tracks: Distinguished Engineers, Principal Engineers, Sun Fellows, Senior Staff Engineers, Directors and Vice Presidents of Engineering, and other senior engineers and executives from any area of Sun are all welcome as Mentors. Potential mentors must be at least principal level; the great majority are at executive level (Director or Vice President or equivalent). SEED Mentors have served from all areas of Engineering worldwide, plus Operations, Sales, Service, Legal, Information Technology, Finance, Human Resources, and Marketing. In creating their Mentor Wish List, each SEED participant needs to make two hard decisions:

  1. What they want to learn
  2. Who has already accomplished the kind of things they want to do
    (that is, who is already down the path that they see themselves walking)

The SEED Engineering mentoring program takes a long-term view and does not have a preference for one kind of learning over another. That is, the mentoring partnership learning does not have to have anything to do with the participant’s current job. Some people want to learn to be better technical managers, others want to know how to get their ideas to customers faster. Many want to improve their soft skills: public presentation or speaking, negotiating, conflict management, and coaching. Still others want to improve their work and family balance and still have a great career. It takes time and mature consideration to work through all of this. Creating the Mentor Wish List is probably the hardest part of the SEED program.

Selecting a mentor based on their Demonstrated Accomplishments is more obviously subjective and time consuming than selection based on Self-identified Competencies. However, in my experience with SEED, there are fewer mis-matches and greater diversity in matched pairs using Demonstrated Accomplishments. Diversity in SEED terms includes demographic, geographic, professional variety. That is, if the mentee feels free to discuss a very broad range of topics, and has an open list of mentors from which to select, communication is encouraged across organizational, professional, geographic, and demographic silos.

grain silos Wisconsin photo: copyright 2009 Katy Dickinson Mentoring can effectively create bridges between professional silos.

Demonstrated Accomplishment vs. Self-identified Competency Selection Systems

Given the disadvantages of a Self-identified Competency Selection System, why would a mentoring program use this option? In short, such a system is relatively easy to automate so it is faster and can support a much larger participant group. That is, it scales: the start-up time is shorter and the administrative overhead is less. There will be more mis-matches but that risk is acceptable in some mentoring programs. For example, if the program is being offered to a large group of junior staff whose potential mentors are just one or two seniority levels above them, the consequences of a mis-match are relatively low. Mentoring@Sun has used a Self-identified Competency Selection System for many successful years.

On the other hand, if the mentees are drawn from a smaller group of high potential, highly promotable, high value staff who will mostly be matched with executive mentors (as is the case with SEED), or are solely from the executive ranks (as is the case in Sun’s new Vice President mentoring program), the consequences from a mis-match are much greater. When the great majority of the mentors are executives, mis-matches are too expensive in terms of wasted time and potential damage to staff and program reputation. A Demonstrated Accomplishment system requires a “high touch” approach consistent with the best way to work with most executives whose time is both limited and valuable. Some program aspects can be automated (such as mentee and mentor application, and match tracking) but the development of each mentee’s potential mentor list is research-intensive and most communications are personal.

A Demonstrated Accomplishment system also needs a very senior mentoring program staff member to act as a broker or matchmaker. The broker needs to be a good communicator to help make a great match. It helps if the broker is well known and has a good reputation so that potential mentors will respond promptly and provide an opportunity for the broker to tell them about the mentee who has requested them. Getting an executive to respond to the first email or even pick up the phone can sometimes be the greatest challenge in making a match.

Images Copyright 2009 Katy Dickinson

2 Comments

Filed under Mentoring & Other Business

Bonduel Village Hall

Visiting family in Wisconsin last week, we several times drove though the Village of Bonduel. Bonduel is between Slab City and Cecil in the dairy farmland near Lake Shawano. I noticed the old brick Fire Station, now used as the Bonduel Village Hall, Library, Police, and Department of Public Works. The more I looked, the odder it seemed.

In addition to the three nuclear Fallout Shelter signs on its walls and the huge siren and silver bell on its roof, this peculiar building is as good an example of remuddling as I have seen. “Remuddling” is a term used by Old House Journal for “misguided remodeling-that is, an alteration that is insensitive to the architecture or character of the house.” Someone decided that colored patchwork fiberglas panels and a huge zigzag steel fascia were just the thing to fill in the old truck bay of what was once a handsome red brick firehouse. Based on the style, the “update” happened in the early 1960s.

Almost as interesting is the building close by with the simple sign HECK. (Heck is where people go who don’t believe in Gosh.)

Fallout Shelter

nuclear Fallout Shelter sign, Bonduel Village Hall, Bonduel Wisconsin<br /> photo: copyright 2009 Katy Dickinson

Bonduel Village Hall

Bonduel Village Hall, Bonduel Wisconsin<br /> photo: copyright 2009 Katy Dickinson

Heck

Heck, Bonduel Wisconsin<br /> photo: copyright 2009 Katy Dickinson

Images Copyright 2009 Katy Dickinson

Leave a comment

Filed under News & Reviews