Title<\/strong>: Plankton Aerosol Clouds and Ecosystem (PACE) Deputy Mission Systems Engineer
Formal Job Classification<\/strong>: Electrical engineer
Organization<\/strong>: Engineering and Technology Directorate, Mission Systems Engineering Branch (Code 599)<\/p>\n
![\"Haghani](\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2017\/02\/noosha_and_tech.jpg\")
<\/a><\/figure>What do you do and what is most interesting about your role here at Goddard?<\/strong><\/p>\n As the PACE deputy mission systems engineer, we solve problems every day, all day long. An advantage I have is that I have been on this project from the beginning.<\/p>\n Why did you become an engineer? What is your educational background?<\/strong><\/p>\n I was always very good at math and science. Both of my parents are engineers. I loved building with Legos and solving puzzles. Becoming an engineer was a natural progression for me.<\/p>\n I have a BS in electrical engineering and a master\u2019s in reliability engineering from the University of Maryland, College Park. I had completed all my course work for my Ph.D. as well but never finished due to family obligations.<\/p>\n How did you come to Goddard?<\/strong><\/p>\n As a freshman in college, I interned at Goddard. After graduation, I worked in industry for a few years. In 2002, I returned to Goddard because I realized that what we do at Goddard is so much more unique and exciting to me.<\/p>\n My mother also works at Goddard as a software engineer, so I am a second-generation Goddard employee. Early on in my career, my mother and I met for lunch occasionally. Now I am just too busy to even schedule lunch.<\/p>\n Describe the advantages you have in understanding a system which you have worked on from the original design through build and testing?<\/strong><\/p>\n I came to the PACE project as the architect of an avionics system called MUSTANG<\/a>, a set of hardware electronics that performs the function of the avionics of the mission including command and data handling, power, attitude control, and more. As the MUSTANG lead, I proposed an architecture for the PACE spacecraft which the PACE manager accepted, so MUSTANG is the core architecture for the PACE spacecraft. I led the team in building the initial hardware and then moved into my current systems engineering role.<\/p>\n Knowing the history of a project is an advantage in that it teaches me how the system works. Understanding the rationale of the decision making we made over the years helps me to better appreciate why we built the system way we did.<\/p>\n How would you describe your problem-solving techniques?<\/strong><\/p>\n A problem always manifests as some incorrect reading or some failure in a test, which I refer to as evidence of the problem. Problem solving is basically looking at the evidence and figuring out what is causing the problem. You go through certain paths to determine if your theory matches the evidence. It requires a certain level of understanding of the system we have built. There are many components to the observatory including hardware and software that could be implicated. We compartmentalize the problem and try to figure out the root cause systematically. Sometimes we must do more testing to get the problem to recreate itself and provide more evidence.<\/p>\n As a team lead, how do you create and assign an investigation plan?<\/strong><\/p>\n As a leader, I divide up the responsibilities of the troubleshooting investigation. We are a very large team. Each individual has different roles and responsibilities. I am the second-highest ranking technical authority for the mission, so I can be leading several groups of people on any given day, depending on the issue.<\/p>\n The evidence presented to us for the problem will usually implicate a few subsystems. We pull in the leads for these subsystems and associated personnel and we discuss the problem. We brainstorm. We decide on investigation and mitigation strategies. We then ask the Integration and Test team to help carry out our investigation plan.<\/p>\n As a systems engineer, how do you lead individuals who do not report to you or through your chain of command?<\/strong><\/p>\n I am responsible for the technical integrity of the mission. As a systems engineer, these individuals do not work for me. They themselves answer to a line manager who is not in my chain of command. I lead them through influencing them.<\/p>\n I use leadership personality and mutual respect to guide the team and convince them that the method we have chosen to solve the problem is the best method. Because I have a long history with the project, and was with this system from the drawing board, I generally understand how the system works. This helps me guide the team to finding the root cause of any problem.<\/p>\n How do you lead your team to reach consensus?<\/strong><\/p>\n Everything is a team effort. We would be no where without the team. I want to give full credit to all the teams.<\/p>\n You must respect members of your team, and each team member must respect you as a leader. I first try to gather and learn as much as possible about the work, what it takes to do the work, understanding the technical aspects of the work and basically understanding the technical requirements of the hardware. I know a little about all the subsystems, but I rely on my subsystem team leads who are the subject matter experts.<\/p>\n The decision on how to build the system falls on the Systems Team. The subject matter experts provide several options and define risks associated with each.\u00a0 We then make a decision based on the best technical solution for the project that falls within the cost\/schedule and risk posture.<\/p>\n If my subject matter experts and I do not agree, we go back and forth and work together as a team to come to a consensus on how to proceed. Often we all ask many questions to help guide out path. The team is built on mutual respect and good communication. When we finally reach a decision, almost everyone agrees because of our collaboration, negotiation and sometimes compromise.<\/p>\n What is your favorite saying?<\/strong><\/p>\n Better is the enemy of good enough. You must balance perfectionism with reality.<\/p>\n How do you balance perfectionism with reality to make a decision?<\/strong><\/p>\n Goddard has a lot of perfectionists. I am not a perfectionist, but I have high expectations. Goddard has a lot of conservatism, but conservatism alone will not bring a project to fruition.<\/p>\n There is a level of idealism in design that says that you can always improve on a design. Perfection is idealistic. You can analyze something on paper forever. Ultimately, even though I am responsible for the technical aspects only, we still as a mission must maintain cost and schedule. We could improve a design forever but that would take time and money away from other projects. We need to know when we have built something that is good enough, although maybe not perfect.<\/p>\n In the end, something on paper is great, but building and testing hardware is fundamental in order to proceed. Occasionally the decisions we make take some calculated risk. We do not always have all the facts and furthermore we do not always have the time to wait for all the facts. We must at some point make a decision based on the data we have.<\/p>\n Ultimately a team lead has to make a judgement call. The answer is not in doing bare minimum or cutting corners to get the job done, but rather realizing what level of effort is the right amount to move forward.<\/p>\n Why is the ability to make a decision one of your best leadership qualities?<\/strong><\/p>\n There is a certain level of skill in being able to make a decision. If you do not make a decision, at some point that inability to make a decision becomes a decision. You have lost time and nothing gets built.<\/p>\n My team knows that if they come to me, I will give them a path forward to execute. No one likes to be stuck in limbo, running in circles. A lot of people in a project want direction so that they can go forward and implement that decision. The systems team must be able to make decisions so that the team can end up with a finished, launchable project.<\/p>\n One of my main jobs is to access risk. Is it risky to move on? Or do I need to investigate further? We have a day-by-day risk assessment decision making process which decides whether or not we will move on with the activities of that day.<\/p>\n As an informal mentor, what is the most important advice you give?<\/strong><\/p>\n Do not give up. Everything will eventually all click together.<\/p>\n What do you like most about your job?<\/strong><\/p>\n I love problem solving. I thrive in organized chaos. Every day we push forward, complete tasks. Every day is a reward because we are progressing towards our launch date.<\/p>\n Who inspires you?<\/strong><\/p>\n The team inspires me. They make me want to come to work every day and do a little bit better. My job is very stressful. I work a lot of hours. What motivates me to continue is that there are other people doing the same thing, they are amazing. I respect each of them so much.<\/p>\n What do you do for fun?<\/strong><\/p>\n I like to go to the gym and I love watching my son play sports. I enjoy travel and I love getting immersed in a city of a different country.<\/p>\n By\u00a0Elizabeth M. Jarrell<\/a><\/strong><\/em> Conversations With Goddard\u00a0<\/em><\/strong>is a collection of Q&A profiles highlighting the breadth and depth of NASA\u2019s Goddard Space Flight Center\u2019s talented and diverse workforce. The Conversations have been published twice a month on average since May 2011. Read past editions on\u00a0<\/em>Goddard\u2019s \u201cOur People\u201d webpage<\/em><\/a>.<\/em><\/p>\n
NASA\u2019s Goddard Space Flight Center<\/a>, Greenbelt, Md.<\/strong><\/em><\/p>\n<\/a><\/figure>\n<\/div>\n<\/div>\n<\/div>\nShare<\/h2>\n<\/p><\/div>\n