<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Abel Almazan on Medium]]></title>
        <description><![CDATA[Stories by Abel Almazan on Medium]]></description>
        <link>https://medium.com/@Jazze?source=rss-ee4f4646ff15------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*co67q0MXP6-fcdT2mJj8IQ.png</url>
            <title>Stories by Abel Almazan on Medium</title>
            <link>https://medium.com/@Jazze?source=rss-ee4f4646ff15------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:31:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Jazze/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[No shortcuts between Tuckman’s team stages]]></title>
            <link>https://tech.new-work.se/no-shortcuts-between-tuckmans-team-stages-26d096b23517?source=rss-ee4f4646ff15------2</link>
            <guid isPermaLink="false">https://medium.com/p/26d096b23517</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[tuckman]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Abel Almazan]]></dc:creator>
            <pubDate>Tue, 21 Jun 2016 07:16:01 GMT</pubDate>
            <atom:updated>2017-04-22T07:52:32.943Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s not easy to see the creation of new teams as often as I have, especially when you work for the same company for several years. I’ve seen teams changing almost completely every year, without many new additions to the employees we already had, which has allowed me to observe how the Tuckman model applies in each particular situation.</p><p>The reason why I could experience the creation of new teams started 2 years ago, with what we name as “Job fair”.</p><p>To quickly summarise, a “Job fair” is: Every year, around January, Product Owners present what the rough roadmap and challenges of each product will be during the incoming year. After that, all the employees have the option to “apply” for a position (1st and 2nd preference) in a team for a particular position and product (I won’t enter into details here, but there could be some constraints which prevent someone to join or leave a team)</p><p>Once the proposed team setups are reviewed and approved, the office is reshuffled and the new team members sit together and are ready to start (if you are especially interested in the “Job fair” concept and want to know more details about it, you can read <a href="https://notesfromanagilist.wordpress.com/2015/03/06/the-job-fair-on-choosing-teams/">the great post</a> that my work mate <a href="https://medium.com/u/7c3fd7858990">astarteny</a> wrote some time ago)</p><h4>From work mates to team mates</h4><p>So, because of the above mentioned, what do we usually have after the “job fair”?</p><p>What we have are new teams formed by a mix of people with different relationships between them, from 2+ people coming from the same former/current team to individuals that never worked directly with any of the new team members nor the product, but all of them have an important thing in common, and is that they know each other quite well because they’ve worked in the same office for the same company for quite a long time.</p><p>This particular situation generated some expectations in the company, in regards to the team stages (forming, storming, norming and performing) defined by the Tuckman’s model, that proved to be wrong.</p><h4>Expectations vs Reality</h4><p>As soon as the new formed teams started, the expectation was that they could skip some, if not all, of the first team stages (mainly forming and storming) and start, from almost the first day, in norming (or even performing) mode, because, as I said, most of them knew each other and some of them already worked together.</p><p>The reality is that some stages take even more time in that situation than for teams built from scratch. Some of the reasons I observed are:</p><p><strong>Forming</strong></p><ul><li>Different levels of product and code knowledge could lead to different speeds and motivation, which would be less evident in a completely new team. The team members that stayed in the team are usually faster building features as they know the codebase and the product, but in some cases they could be less motivated than the newcomers because their chance to learn is much lower, among other reasons.</li><li>It could happen that some team members were already working in the same former team, so you could end up having sub-teams inside the team, which could slow down building a full team spirit and team commitment.</li></ul><p><strong>Storming</strong></p><ul><li>Roles are unclear which could lead to a conflict of interests as some people might like to preserve the role they had in the former team, but ends up as duplication of roles in most of the cases. That’s especially problematic when those duplicated roles have some kind of decision power, like Tech Lead or QA Lead.</li><li>Team lacks of processes as a new group, as it is expected in that stage, but the parts come with suggestions from what it worked in their former teams, that in some cases could be contradictory or not even valid with the new setup, so long discussions could happen and final agreement is usually not easy.</li><li>If the “sub-teams vs. Team” situation mentioned in the Forming section above was not solved already, it could be even more evident and magnified here, which could damage the team and prevent it to move forward to the next stage. From my experience and observations, is more difficult to arrive to an agreement and resolve conflicts (expected at this stage) when the parts in conflict are groups of people instead of individuals.</li><li>Especially at this stage, and because of what I mentioned above, it is very important to count with a good leadership style that works hard on building trust and good relationships between team members, by giving support on resolving conflicts and influencing a positive attitude towards finding solutions to problems.</li></ul><h4>Conclusions</h4><p>Even if it could seem like it is possible, what I observed is that there are no shortcuts for the path between Forming and Performing. It doesn’t matter if the members of the team knew each other previously, most of the times they will have to go through all the stages until they are a performing team.</p><p>It could happen that the time needed for each stage and the jumps between stages are completely different for these kinds of teams than for the ones formed from scratch, but that doesn’t mean that it will take less time or that they could skip stages</p><ul><li><a href="https://www.mindtools.com/pages/article/newLDR_86.htm">Understanding the Stages of Team Formation</a></li><li><a href="http://www.leadershipthoughts.com/team-building-and-situational-leadership/">What Everybody Ought to Know About Team Building and Situational Leadership</a></li><li><a href="https://notesfromanagilist.wordpress.com/2015/03/06/the-job-fair-on-choosing-teams/">The Job Fair: On Choosing Teams</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26d096b23517" width="1" height="1" alt=""><hr><p><a href="https://tech.new-work.se/no-shortcuts-between-tuckmans-team-stages-26d096b23517">No shortcuts between Tuckman’s team stages</a> was originally published in <a href="https://tech.new-work.se/">New Work Development</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Feature addiction]]></title>
            <link>https://medium.com/@Jazze/feature-addiction-10ea2779a0a7?source=rss-ee4f4646ff15------2</link>
            <guid isPermaLink="false">https://medium.com/p/10ea2779a0a7</guid>
            <category><![CDATA[tracking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Abel Almazan]]></dc:creator>
            <pubDate>Wed, 28 Oct 2015 08:42:35 GMT</pubDate>
            <atom:updated>2017-02-11T21:50:35.569Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s been a while since I have been thinking on writing about this topic and reading from time to time some articles related to it. I have to say that it has been a recurring topic in almost every company I’ve worked for. I’m talking about the “addiction” to add features to products, and the aversion to remove them.</p><p>Then, we had a big retrospective (an awesome one, I have to say) at Xing, where more than one of the topics that came up (mainly product/feature life-cycle) were, to a certain extent, related to what I’ve been seeing during my professional experience.</p><p>That being said, I decided that it was the right time to write about it and give my thoughts and opinion.</p><h4>From my experience</h4><p>I’ve worked in a startup and in small/medium companies and in all of them I’ve seen the same behaviour: always adding features, rarely improving and/or maintaining (just bug fixing from customer complaints), and never (yes, never) removing any of them.</p><p>Also, the features added were, most of the time, ideas coming from management or stakeholders, without much validation with potential customers/users about if that was the right feature to solve the needs that users had or even if there is a real need of that feature.</p><p>The most extreme example of that was when I was asked by management (I was developer at that time), when showing the final version of the landing page to them, to think about some feature to fill an empty space on the right column (it was there because the main content column, which was dynamic, was longer than the right column content, fixed one).</p><p>With this example you can see how underestimated is, sometimes, the cost of a feature, and how adding a feature is, almost always, perceived as a good thing for the product and the final user, which, as we will see later in this article, is not always the case.</p><p>As I said, what I’ve seen a lot is how companies create features (or even complete products) based on some market research on the needs/problems to solve, done previous to the feature definition phase, but without much (if any) validation with users/customers during the development, by means of user tests or launching to beta testers before going live to all users, among others.</p><p>Then, the feature is launched, without much information about if that will fit with user needs or if the user knows how to use it. But then it gets even worse when this feature is “abandoned” there, with no further iteration on improving it, with no A/B tests to compare if some change in the UI could improve the usage and with no tracking to be able to even measure if it’s actually used.</p><p>And usually, the main reason of that way of working is the feature addiction itself, because we have 10 more features in our backlog (most of the times with the same amount of validation from users) that have to be released as part of our roadmap. Let’s say that the feature life-cycle is missing some important steps and is frozen in its adolescence, right after releasing it.</p><p>But there is an extra point which is the cost of adding features indefinitely. We can’t forget that each feature added to the product has some costs apart from development. One important cost is the maintenance of the product, like bug fixes, technology stack upgrades, etc. which grows as much as the number of features you have. Another cost of adding a feature after the other is technical debt (especially if you add the “deadline” factor), as there is usually no time allocated for improvement between releases, with leads into bug prone products and slow development speed.</p><p>So, we can say that all the missing steps on the feature life-cycle mentioned above are important, but there is one which is key, and it is tracking. Why?. Because without tracking you can’t measure how well a change you apply is doing and even more important, how a feature is performing, and without that information you can’t decide if a feature should be killed or not. That explains (among other reasons) the aversion to remove features, which is the next point I would like to deepen</p><h4>PHOBIA TO KILL FEATURES</h4><blockquote><em>Perfection is attained not when there is nothing more to add, but when there is nothing more to remove.</em></blockquote><blockquote><em>ANTOINE DE SAINT-EXUPERY</em></blockquote><p>There are several reasons why you should be considering removing a feature from your product. A reason could be that the feature is not used (maybe because the need was not validated during definition phase). Another reason could be that the feature is kind of outdated because is not oriented any more towards the vision and mission of the company and/or to the value proposition of your product.</p><p>I found also the following reasons in a post called <a href="http://www.mindtheproduct.com/2011/08/to-kill-a-feature/">To Kill a Feature</a> which are also interesting:</p><ul><li><em>It’s costing you users</em> — Too many options in your product that makes it difficult to focus on the main function.</li><li><em>It’s blocking the effectiveness of another feature</em> — Maybe a feature is overlapping another one, or taking value from one included in you premium option.</li><li><em>It’s costly to keep up — </em>the ROI on a feature that is barely used is too low to keep it</li></ul><p>But, as I said previously, the most important thing is to be able to know that a feature is not used and why, because as bad as adding without validation is removing them without objective data that supports this act.</p><p>So, why is it so hard to remove them? From my experience in companies, the main reasons are (among others):</p><ul><li><em>The lack of data that supports the decision</em> — as I said, you need tracking to measure and decide</li><li><em>Customer complaints</em> — having to deal with some customer complaints that are still using it</li><li><em>Sense of failure — </em>if you keep them live is not that explicit that it was a bad decision to build them</li><li><em>Technical dependencies</em> — not having complete control on how that affects the code and manage the dependencies, i.e other parts of the product and other teams</li></ul><p>What about the cost of not removing them? We said that “<em>It’s costly to keep up</em>” an unused feature, but where are the costs coming from? Just to enumerate some that come to my mind:</p><ul><li>There is a maintenance implicit, like on design changes, to adapt them. Also on technology stack upgrades, bug fixes. It adds complexity to the code. The time spent on executing (and maintaining) the test suite is also higher.</li><li>The excess of features — The unused features add complexity and “noise” to the product’s value proposition (never forget the KeepItSimple claim). That annoys the customer who could go for a more simple and focused product if it exists, and leave yours.</li><li>The more a product is crowded with (unused) features the more difficult is to add new (valuable) ones without breaking the usability.</li></ul><blockquote><em>Your users probably have very little time to sift through piles of options or user guides to figure out how to accomplish what they signed up for in the first place. If they can’t figure this out quickly and easily, they’ll walk away</em></blockquote><blockquote><em>JANNA BASTOW</em></blockquote><h4>Conclusions</h4><p>As a conclusion and summarizing, I would say that you have to take care of the whole feature lifecycle, not just on the creation phase. It’s easy to underestimate the real cost of adding a new feature, which starts with definition and implementation, but ends with maintenance (adding time to QA on every change done around them), bug fixing, design changes, etc.</p><p>Also I wouldn’t use gut feeling or just company goals (and KPI) when creating new features.</p><ul><li><strong>Validate your assumptions with users</strong></li><li>Check if <strong>that feature goes in the direction of solving their problems or needs when defining it…</strong></li><li>…but even more important, <strong>don’t forget about the feature after launch</strong>. Use tracking, A/B test, etc to see how small changes increase/decrease the usage and user satisfaction.</li><li>and if looking at the data you still have doubts, <strong>think about the possibility of removing the feature temporarily and see user reactions</strong>, and always be ready to return it back (be courageous, make mistakes and learn from them). If you were wrong, check why. Sometimes the reason could be bad placement (so it’s not seen by all users or forgotten) or needs a tweak on the UI (not easy to use or not understood by everyone)</li></ul><p>By doing all said above, you will have enough data to decide if a feature is worth keeping or if you must kill it, and if so, do it for the sake of product/code simplicity, maintenance and costs.</p><h4>Related reading and videos</h4><ul><li><a href="http://www.mindtheproduct.com/2011/08/to-kill-a-feature/">To kill a feature by Janna Bastow</a></li><li><a href="http://www.erickarjaluoto.com/blog/you-keep-using-that-word-mvp/">You keep using that word: MVP</a></li><li><a href="http://www.mindtheproduct.com/2015/09/video-the-root-causes-of-product-failure-by-marty-cagan/">The Root Causes Of Product Failure by Marty Cagan [VIDEO]</a></li><li><a href="http://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation/dp/0307887898/">The Lean Startup by Eric Ries [BOOK]</a></li><li><a href="http://www.amazon.com/Inspired-Create-Products-Customers-Love/dp/0981690408/">Inspired by Marty Cagan [BOOK]</a></li></ul><p><em>Originally published at </em><a href="https://jazzeblog.wordpress.com/2015/10/28/feature-addiction/"><em>jazzeblog.wordpress.com</em></a><em> on October 28, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10ea2779a0a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Commitment as one of our values]]></title>
            <link>https://medium.com/@Jazze/commitment-as-one-of-our-values-a1d078f6adec?source=rss-ee4f4646ff15------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1d078f6adec</guid>
            <category><![CDATA[values]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[commitment]]></category>
            <dc:creator><![CDATA[Abel Almazan]]></dc:creator>
            <pubDate>Wed, 26 Aug 2015 15:08:58 GMT</pubDate>
            <atom:updated>2016-03-06T15:02:17.078Z</atom:updated>
            <content:encoded><![CDATA[<p>Let me give you a bit of context first.</p><p>Some months ago we had our first offsite as the new leadership team, formed by 6 people, which is in charge to lead a business unit held in Barcelona with around 40 people.</p><p>One of our topics for that offsite was to come up with which are/should-be our values, not only as a company (we already have some values coming from our HQ in Hamburg), but specially as an office/business-unit.</p><p>After some discussions, we agreed on 5 values that we thought we all should have in mind when working and collaborating with each other.</p><p>It turned out that one of our values was <strong>commitment</strong>.</p><p>So, after some months of no action in relation to how to influence those values, I committed (yes, how not) on reading and summarize some info on that value and present it to the rest of the leadership team in order to start working on it.</p><p>In this post I would like to summarize my learnings on this topics plus giving my own contribution to it from my own experience</p><h4>What does commitment mean?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*ljeIgoWCLMzEXwuX." /></figure><p>After reading some material about the topic I <a href="http://ctb.ku.edu/en/table-of-contents/leadership/leadership-functions/build-sustain-commitment/main">found this definition</a> that I think matches quite well what I also understand about commitment:</p><blockquote><em>Commitment is dedication to a particular organisation, cause, or belief, and a willingness to get involved.</em></blockquote><p>We (the leadership team) focused on the “belief” in the sentence, which is the the one that we think is important. At the end, you commit to something you believe. It could be an organization, a project or even a feature, but it has to be something that motivates you and that you think is significant and other people will benefit from.</p><p>If you get your company employees believe in what the company is doing or contributing to society, you will most probably get them onboard and committed. After all, committed employees are vital for any company where the tasks to be done are not simple and require an extra effort, sometimes out of working hours, even if it’s just continue thinking about a solution to a particular problem when already at home.</p><p>But there is not only committed or not. According <a href="https://www.readability.com/articles/un1qotpb">to this article</a>, there are other two positions in regards to the company that an employee could adopt: <strong>Resistance</strong> and <strong>Compliance</strong>.</p><p><em>Resistance</em> means direct opposition to what the company thinks is the best approach. It could be that they say yes to the idea but then make excuses about why it can’t be done.</p><p><em>Compliance</em> which means that the person will do whatever is told to him but with the minimal effort. He will just accomplish what is asked to him but with the minimum involvement and initiative. That’s better than Resistance, but far from ideal.</p><p>I would say (from my experience) that resistance is less common, but I think you can find several employees in the compliance mode, maybe not all the time but in certain moments, depending on the particular goal that the team or company has.</p><p>So, one of the goals of a company (and a leadership team) should be finding out how to bring this people from compliance to committed, in other words, how to influence commitment.</p><h4>Characteristics of a committed employee</h4><p>I would like to summarize, from all the readings, what are the main characteristics a committed person has:</p><ul><li><em>Strong Work Ethic</em>: They take initiative to complete tasks, and don’t need their bosses continuously reminding them what’s next on the agenda (Self Organized and disciplined)</li><li><em>Sense of responsibility</em>: Employee feels responsible of her performance and so acts in consequence by showing up on time to work, puts a lot of effort and applies her best abilities to fulfill the projects on time</li><li><em>Discipline</em>: An employee with good discipline stays focused on his goals and is determined to complete his assignments</li><li><em>Passion</em>: “When an employee believes strongly in the company’s mission, their job is no longer a job. People work harder when they feel connected to and believe in your mission as a leader and the mission of the company.”</li></ul><p>I would say that if your employees don’t have any of these characteristics, it will be hard if not impossible to influence commitment, so, I think it is very important to look for them in your hiring process.</p><h4>How to influence commitment then?</h4><p>Now is time to influence commitment, but, when we started to talk about it, we noticed that the first thing to do is to see which level of commitment we have as a leadership team, because, If we are not as committed as we should, how can we influence commitment to the rest of the organization?!?</p><p>Is known that the relationship between leadership and employees influences a lot the level of commitment (actually on both). We are already doing bi weekly 1:1s, attending daily scrums, sitting in team spaces instead of isolated, etc. to be involved and close to them, and I would say the relation is quite good. But, of course, there is always room for improvement.</p><p>One of the first things to do could be paying attention to employees needs , based on the pyramid of needs at work (see <a href="http://www.bizjournals.com/charlotte/stories/2003/09/01/smallb6.html">Committed employees can create winning organization</a>)</p><p>It basically says that…</p><blockquote><em>When employees feel safe and secure in the workplace, when they feel they are compensated for their performance, feel pride and spirit in the organization, perceive personal and organizational growth opportunities, and perceive balance between job and personal demands, employees commitment is at its highest.</em></blockquote><p>And without meeting employee expectations on the lowest level of need, the next-higher level doesn’t really affect commitment</p><p>So we could check, for example, through 1:1s, how covered are each of the needs on every employee and define actions from there.</p><p>Another interesting read is about the three components that define the relationship between an employee and the company (from <a href="http://www.mindtools.com/pages/article/three-component-model-commitment.htm">The Three Component Model of Commitment</a>] for more info)</p><p>It says that there are three components:</p><ul><li>Affection for your job (“<em>affective commitment</em>“): strong emotional attachment to your organization</li><li>Fear of loss (“<em>continuance commitment</em>“): the loss you’d experience by leaving it is greater than the benefit you think you might gain in a new role</li><li>Sense of obligation to stay (“<em>normative commitment</em>“): feel that you should remain with your organization because it has invested money or time in your training or a reward in advance</li></ul><p>… and an employee usually has the three of them, but in different degrees.</p><p>For the company, it’s kind of easy to increase the continuance and normative level, but actually our main goal should be to influence the affective one, which is, again, based on belief on the company/product, passion/motivation, sense of contributing to something significant and valuable, etc.</p><p>Another important, if not the most one, is that people is happy at work (and at life, of course), so we, as the leadership team, should take all the actions that are in our hands to achieve that. My colleague <a href="https://medium.com/@astarteny/">Mel</a> sent me <a href="http://www.happymelly.com/the-12-steps-to-worker-happiness-and-beyond/">THE 12 STEPS TO WORKER HAPPINESS, AND BEYOND!</a>, where there is a “guide” to happiness at work with 12 steps, all really important to me, but the ones I think we can influence more are the following:</p><ul><li>Aim for a goal and get people to understand and realize their own purpose. Involving your employees in the company objective will give them purpose, which in turn increases motivation levels.</li><li>Experience new things, try stuff out, and let people run all kinds of experiments. Real innovation comes from employees, not management.</li></ul><p>Those two are also aligned with the explained above, related to the purpose of what we do and the motivation.</p><h4>Let’s take action</h4><p>We talked a lot about commitment, but which actions could we take to start influencing it in the office?</p><p>The first actions, after talking about it, were more related to us as the leadership team. After all, if we want to influence commitment, we have to be committed first.</p><p>So we had the “task” to find out our personal commitment as individuals but also ask in our 1:1s to our people. So the question was if we believe in what we do as an organization, so we can extract from there the current level of commitment.</p><p>No need to say that to get a honest answer to that question, people need to have a good relationship with his/her line manager and no fear. Have to say that I already asked to some and the answers were really honest, which for me means that they have confidence on me to talk openly about their opinion (and I’m very glad about it :) )</p><p>Back to the task, when it comes to us, the leadership team, we had a meeting after a week and it turned out that some of us didn’t believe in some of the big features planned for the year, so we asked the Product team to give us more details, clarify and convince, in a way. That was the only action we took from the leadership team, which seems, at least to me, not enough, and I would us to work a bit more on our own commitment in the next weeks.</p><p>Regarding the outcome from asking our people about their belief in the organization, we haven’t had a meeting in order to guess in which level of commitment we see each of our team members. I’m missing that and I think is something we will have to do soon. That will also help to understand and group the reasons why they are more, or less, committed and then take some actions to work on those reasons.</p><p>One of the main reasons why we still haven’t had this meeting is because of a deadline that keeps all of us really busy, but I also have to say that the topic is not trivial at all, and needs quite a lot of time and effort even if is just to start influencing and improving.</p><p>Said that, my plan is to write a second part of this post as soon as we had taken more actions and have real first hand experience on the topic.</p><p>In any case, and while waiting for our own actions from experience, I want to put here some other potential actions that could be taken to increase commitment, most of them extracted from <a href="http://ctb.ku.edu/en/table-of-contents/leadership/leadership-functions/build-sustain-commitment/main">Building and Sustaining Commitment</a>:</p><ul><li>Be open and clear about the mission, principles and goals for the company</li><li>Model commitment as a leader</li><li>Pick out the right level of challenge for people</li><li>Try to match people with work where they can achieve some success and then give them gradually increasing challenges</li><li>Build a culture of respect and esteem</li><li>Listen, listen and listen</li><li>When you listen to others with respect, they sense that you have confidence in them and are interested in what they think.</li><li>Create a “healthy workplace” — there are five main factors that contribute to workplace health:</li></ul><ol><li>The physical environment (including health and safety).</li><li>Employee growth and development.</li><li>Recognition.</li><li>Employee involvement.</li><li>Life balance.</li></ol><ul><li>Celebrate</li></ul><h4>Materials used</h4><ul><li><a href="http://ctb.ku.edu/en/table-of-contents/leadership/leadership-functions/build-sustain-commitment/main">Chapter 14. Core Functions in Leadership | Section 5. Building and Sustaining Commitment | Main Section | Community Tool Box</a></li><li><a href="http://www.mindtools.com/pages/article/three-component-model-commitment.htm">The Three Component Model of Commitment — From MindTools.com</a></li><li><a href="https://www.readability.com/articles/un1qotpb">Influence: Gaining Commitment, Getting Results — The Human Resources Social Network</a></li><li><a href="https://www.linkedin.com/pulse/20130723160110-658789-7-qualities-of-a-truly-loyal-employee">7 Qualities Of A Truly Loyal Employee | Dharmesh Shah | LinkedIn</a></li><li><a href="https://www.readability.com/articles/udhaaaeg">Qualities of a Committed Employee — Woman</a></li><li><a href="http://www.relationshipcoachinginstitute.com/role-of-commitment-in-coaching-relationships/">Role of Commitment in Coaching Relationships — Relationship Coaching Institute(RCI)</a></li><li><a href="http://www.bizjournals.com/charlotte/stories/2003/09/01/smallb6.html">Committed employees can create winning organization — Charlotte Business Journal</a></li><li><a href="http://www.happymelly.com/the-12-steps-to-worker-happiness-and-beyond/">THE 12 STEPS TO WORKER HAPPINESS, AND BEYOND!</a></li></ul><p><em>Originally published at </em><a href="https://jazzeblog.wordpress.com/2015/08/26/commitment-as-one-of-our-values/"><em>jazzeblog.wordpress.com</em></a><em> on August 26, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1d078f6adec" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>