Skip to content
Tiatra, LLCTiatra, LLC
Tiatra, LLC
Information Technology Solutions for Washington, DC Government Agencies
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact
 
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact

6 tips for successfully leading software developers

Developers are notoriously grumpy and unamenable to disruption.  They tend to want to continue working until they arrive at a place of completion and satisfaction. 

That’s all well and good unless they’ve lost sight of the bigger picture.

What’s an IT leader to do?

The following perspectives will help you better understand what motivates and mystifies developers and can guide your thinking on how to be the leader your team needs.

Cultivate business awareness

One of the critical tasks for all leaders is to provide an overhead strategic vision to the people who work on the lower-level tasks.  This is especially important—and challenging—when working with developers because their work is so demanding of careful, focused attention. 

Developers are required to master an enormous amount of complexity that can squeeze out the larger context, resulting in a kind of myopia.  The work itself is enough to occupy even the most ambitious and active mind, so it becomes especially important for leaders to provide the two-way channel between the daily coding and the larger direction.

This is a delicate task. 

Asking for progress reports or offering direction or, worst of all, changing course, are all typically most unwelcome.  In some cases, these are actually very disruptive, but in others, they are exactly what is needed. 

The right way to engage developers in strategic dialog is in a balance.  Here is where meta-engagement is important.  Asking developers about how the meeting load is, and how well they feel engaged in the larger goals is a good way to tune the balance.   It also helps to get them thinking about the bigger issues.

Cultivating developers who have both technological excellence and business awareness is a hugely precious thing to the leader, the business and the developer. 

Convey meaning

Although strategy and business value are valuable to communicate to developers, there is an even higher thing which we’ll call purpose or meaning.  The strategy is engaged to support the mission.  The mission is the raison d’etre for the company itself. 

Does the company have a potent mission statement?  Is the essence of the mission well distributed into the ranks?  The rightness or goodness of the enterprise should be infused into everyone’s activity.

Developers are especially tricky, as they are typically rather resistant to what they often cynically see as indoctrination.  Nevertheless, the sense of legitimacy is just as necessary for long-term developer contentment as anyone else. 

The key to delivering meaning to developers is to understand the next point about creativity—and integrating it.  The inherent worth that developers derive from coding can be integrated with the larger business purpose.  Uniting meaning and creativity is a major source of a drive for excellence for developers.

Foster creativity

Developers’ will to create is strong, but it can be hard to perceive as creativity is often obscured by the technological nature of development.  Developers communicate with a strange patois of acronyms that hide the artistic spirit behind it.  Learning to perceive and nurture that spirit is a special kind of leadership that developers will appreciate.

Just the awareness of the creative life of developers is important.  Not only will it help to understand where they are coming from, but it will lead to policies and decisions that support that creativity and out of that will come real bottom-line benefit.  The space and time to innovate will lead to better software that handles the vicissitudes of business.  You need the human creativity of your developers captured in the half-machine/half-thought medium of code to be agile.

Perhaps the most important feature for the leader to bear in mind here is in realizing the attachment that developers have to their work.   Affection might be a better word than attachment.  Building a thing that feels beautiful and worthy in itself has its own momentum.  Interrupting this momentum should be undertaken with a soft touch, rather than as if switching tabs in the browser.  If possible, a gradual readjustment is best.

Developers work with machines, but they are not themselves machines.  At the same time, improving developers’ understanding of the larger context as discussed above is greatly helpful in bringing out an understanding of the necessity for redirection, tuning, and planning.  This understanding helps to ameliorate the frustration and feeling of senseless churn.

Allow space for failure

Despite their mastery of complexity, developers are prone to feeling like they are not really up to the job at hand—the strange phenomenon known as imposter syndrome.

This kind of insecurity is more common and sensible with green developers, but you would be surprised at the accomplished programmers who still acknowledge running into it.  Even coders coming from great success can find themselves burdened with uncertainty about their ability to handle the next thing confronting them.

Every leader’s style is different, of course.  So is every developer’s.  Instead of a hard and fast rule like avoiding harsh criticism or promoting recognition, it’s good to simply bear in mind the kind of difficulty developers wrangle with in their daily work.  The path of execution is rarely a straight line for a developer.  They frequently must call upon an inspirational force to get there, and this can be frightening when deadlines loom.

Even if you think there is no way that a person is uncertain about their ability to execute, it’s helpful to remember that at some point they were.  They are confident because they have come through it and developed mechanisms for dealing with it. 

In addition to awareness on the part of leaders, a good approach to helping is to encourage communication between developers as described in this Tweet.  In short, encourage senior developers to share their experience with juniors, especially with a willingness to acknowledge mistakes. 

The ability to air mistakes in a safe environment is therefore an important thing for leaders to cultivate.  Provide the ability to fail forward, with a sense that guardrails are in place, and developers will thrive.  Failure is an important part of all enterprise and innovation, and especially so for developers.

Encourage taking breaks

Here is a practical insight: When you have developers who are facing blocks, they have a tendency to beat their heads against the wall of impasse.  Usually, the block is a creative one that can’t be solved with faster shoveling and hammering.

Know when to encourage a break.  It’s counterintuitive, but so many times the breakthrough a programmer is looking for is not to be found in working harder but in getting some distance from the problem.

Developers themselves frequently miss this point.  In fact, they will actively resist it when they are in the grips of a tough challenge.  They believe that continuing to grind away at the thing is the path to a breakthrough.

Even though time and time again they will struggle against a seemingly intractable difficulty, believing that further effort will yield result, only to take a begrudging pause in the effort and then suddenly envision how the whole issue can be resolved.  Like a stroke of lightning, everything crystallized and seemed so obvious. 

Sometimes what seemed like a systemic shortcoming—a flaw in the design perhaps—turns out to be a face-palm like a botched variable capitalization.

By being outside the trenches, you can help keep in mind what the developers themselves forget: the non-linear nature of their work.  Success is a union of effort and creativity.  Sometimes the goal can’t be reached by further direct effort and must await more insight.  Be a leader who can help remember this and your developers will thank you.

Provide balance

Developers suffer from discontentment, stress, and burnout at a high rate.  Whatever you can do to mitigate this is welcome.  Developers do it to themselves and also are subject to external pressures. Both of these forces can be addressed by leaders.

Internally, developers suffer from a kind of obsessive tendency about programming.  In some ways this seems beneficial for the enterprise: Keep the devs caffeinated and coding.  But predictably, that is a recipe for burnout. 

If you can be the voice of balance in developers’ work lives, you will benefit both them and the business.  The best way to do this is to be a softening shield when bridging between them and the pressures of the business.  Often, it’s not more pressure but a sense of support and guidance that is most in need.

Developer, IT Leadership, IT Management


Read More from This Article:
6 tips for successfully leading software developers
Source: News

Category: NewsSeptember 16, 2022
Tags: art

Post navigation

PreviousPrevious post:70% of legal departments don’t invest in digital transformation: ReportNextNext post:5 Tips to Help Create a Winning Grocery Loyalty Program

Related posts

휴먼컨설팅그룹, HR 솔루션 ‘휴넬’ 업그레이드 발표
May 9, 2025
Epicor expands AI offerings, launches new green initiative
May 9, 2025
MS도 합류··· 구글의 A2A 프로토콜, AI 에이전트 분야의 공용어 될까?
May 9, 2025
오픈AI, 아시아 4국에 데이터 레지던시 도입··· 한국 기업 데이터는 한국 서버에 저장
May 9, 2025
SAS supercharges Viya platform with AI agents, copilots, and synthetic data tools
May 8, 2025
IBM aims to set industry standard for enterprise AI with ITBench SaaS launch
May 8, 2025
Recent Posts
  • 휴먼컨설팅그룹, HR 솔루션 ‘휴넬’ 업그레이드 발표
  • Epicor expands AI offerings, launches new green initiative
  • MS도 합류··· 구글의 A2A 프로토콜, AI 에이전트 분야의 공용어 될까?
  • 오픈AI, 아시아 4국에 데이터 레지던시 도입··· 한국 기업 데이터는 한국 서버에 저장
  • SAS supercharges Viya platform with AI agents, copilots, and synthetic data tools
Recent Comments
    Archives
    • May 2025
    • April 2025
    • March 2025
    • February 2025
    • January 2025
    • December 2024
    • November 2024
    • October 2024
    • September 2024
    • August 2024
    • July 2024
    • June 2024
    • May 2024
    • April 2024
    • March 2024
    • February 2024
    • January 2024
    • December 2023
    • November 2023
    • October 2023
    • September 2023
    • August 2023
    • July 2023
    • June 2023
    • May 2023
    • April 2023
    • March 2023
    • February 2023
    • January 2023
    • December 2022
    • November 2022
    • October 2022
    • September 2022
    • August 2022
    • July 2022
    • June 2022
    • May 2022
    • April 2022
    • March 2022
    • February 2022
    • January 2022
    • December 2021
    • November 2021
    • October 2021
    • September 2021
    • August 2021
    • July 2021
    • June 2021
    • May 2021
    • April 2021
    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    Categories
    • News
    Meta
    • Log in
    • Entries feed
    • Comments feed
    • WordPress.org
    Tiatra LLC.

    Tiatra, LLC, based in the Washington, DC metropolitan area, proudly serves federal government agencies, organizations that work with the government and other commercial businesses and organizations. Tiatra specializes in a broad range of information technology (IT) development and management services incorporating solid engineering, attention to client needs, and meeting or exceeding any security parameters required. Our small yet innovative company is structured with a full complement of the necessary technical experts, working with hands-on management, to provide a high level of service and competitive pricing for your systems and engineering requirements.

    Find us on:

    FacebookTwitterLinkedin

    Submitclear

    Tiatra, LLC
    Copyright 2016. All rights reserved.