<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:blogger='http://schemas.google.com/blogger/2008' xmlns:georss='http://www.georss.org/georss' xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-1593068256845109312</id><updated>2026-08-07T07:58:46.097-07:00</updated><category term="Technology Management"/><category term="Organizational Theory"/><category term="Innovation"/><category term="Entrepreneurship"/><category term="Jobs"/><category term="Software Engineering"/><category term="Agile Methodologies"/><category term="Human Dynamics"/><category term="Excellence"/><category term="Learning"/><category term="Personal Finance"/><category term="C++"/><title type='text'>Flux.i.r</title><subtitle type='html'>Embrace The Flux</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default?start-index=26&amp;max-results=25&amp;redirect=false'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>95</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-3102458266423470745</id><published>2020-07-31T04:38:00.000-07:00</published><updated>2020-07-31T04:39:21.698-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Agile Methodologies"/><category scheme="http://www.blogger.com/atom/ns#" term="Human Dynamics"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>My Scrum Journey – In the Beginning</title><content type='html'>&lt;div&gt;&lt;b&gt;Context&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;A couple of years ago, I attended a Scrum training that was so kindly sponsored by a previous employer. At that time, I have already been practicing Scrum (which I now know actually wasn’t) in some form or another for seven or so years. So, understandably, I was excited (despite my bias against classroom-type training) to finally learn the fundamentals I felt I was lacking. Unfortunately, instead of laying a foundation, the training ended up getting me even more confused. And this sense wasn’t exactly isolated. As a former colleague humorously put it, many felt they knew less about Scrum after the training than before.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Here are some claims the trainer made that I found questionable:&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- The Scrum Master and Product Owner are not part of Scrum Team (he probably meant the Development Team)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- Sprint 0 is a good/useful practice&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- QA is done outside the development team&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- UX involvement is only needed at the end of the Sprint&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Looking back, as bad as that training was, it turned out to be the best training I attended in a long time (if not, ever). Not because of the delivery and definitely not because of the content but because of what it awakened in me, a desire to go back to the basics, to take it upon myself to answer the question “What is Scrum?” and to practice Scrum as faithfully as its creators intended; not because I think they are infallible but because of a sincere desire to really learn, master and ultimately adapt it (nobody wants dogma or to be dogmatic – to follow blindly – but &lt;a href=&quot;https://martinfowler.com/bliki/ShuHaRi.html&quot;&gt;Shu-Ha-Ri&lt;/a&gt;: follow the rule, “break” the rule, be the rule). So, in a very real sense, it set me on my Scrum journey.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;(And, who’s to say that that wasn’t in fact the intent of the trainer. Perhaps, he really is a Scrum Master!)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;What follows are some of my notes in the beginning of that journey (which I wrote some days after the training); mostly taken from the Scrum Guide and some articles and videos I have encountered online (that I unfortunately failed to note down). Those in italics I have added more recently.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;(I have since moved on from the Scrum Guide to &lt;a href=&quot;http://scrumbook.org/&quot;&gt;Scrum Patterns&lt;/a&gt; and I feel I have barely scratched the surface in gaining that depth of understanding that true masters possess.)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Brief History of Scrum&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- more than 20 years old; created around the 90s, has evolved since -- latest incarnation is defined by the &lt;a href=&quot;https://www.scrumguides.org/scrum-guide.html&quot;&gt;Scrum Guide&lt;/a&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- created by Ken Schwaber, Jeff Sutherland; Mike Beedle also a pioneer, all three are among the 17 original signatories of the &lt;a href=&quot;http://agilemanifesto.org/&quot;&gt;Agile Manifesto&lt;/a&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- actually predated the agile manifesto; but conceptually based on it (but more so -- both historically and conceptually -- on Lean or more accurately, the Toyota Production Systems)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Side Topic: Agile Manifesto&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- around the time the manifesto was written, waterfall was still the dominant software development methodology&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- but there was a growing movement away from it; there were already distinct agile &quot;ways&quot; e.g. XP, DSDM, Crystal, Scrum&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- basically, these &quot;new ways&quot; of doing software development was a reaction to waterfall and its perceived shortcomings:&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; big upfront planning + big release at the end of a long (several months long, even years) development phase resulted in delays, cost overruns and outright failures&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; traditional project management&#39;s focus on standard/stringent/heavy-weight processes and treatment of people as interchangeable/replaceable &quot;resources&quot;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- founders/creators/thought leaders on these &quot;new ways&quot; gathered and realized that though they have differences, they agree on a lot of things and have come to strikingly similar conclusions on how to do software development better&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- the result was the agile manifesto - a distillation to the essence of these &quot;ways&quot; -- a set of values and principles that elaborate the values; so in way, agile is a mindset&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- in many ways, agile is the polar opposite of waterfall:&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; people are the most essential; each one is unique and brings a unique value to the table -- they&#39;re not replaceable (in the sense that say servers are)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Side Comment: Agile for me is all about tightening feedback loops and continuous learning and experimentation.&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Back to Scrum: So What is Scrum?&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;A framework...&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- it is a FRAMEWORK, not a methodology, not a technique&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- analogy: building construction: foundation (agile manifesto values) + framework/structure (scrum) + exterior/interior design/details (methodology + practices + techniques)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- a methodology is more prescriptive with specific processes/practices/instructions; a framework can be built upon, filled in, though it also identifies boundaries/limits/restrictions such that when you go beyond them you are already outside of the framework&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; this will be made clearer later on&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;...for addressing problems and delivering solutions/value&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- but a framework for what? a framework for addressing complex ADAPTIVE problems (such as developing software) and productively and creatively delivering the highest possible VALUE (i.e. value-optimizing)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- it is iterative and incremental; iterative pertains to the &quot;process&quot; and means repetition of activities (paulit-ulit), incremental pertains to the result and means building on top of past results (paunti-unti)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- what does iterative and incremental development enable? agility, flexibility, adaptation, changing course..why? (explain -- see pillars)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;The Scrum Team&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- the essence of Scrum is a small, stable and autonomous team of people -- the individual team is highly FLEXIBLE and ADAPTIVE&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- they collaborate and interoperate&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;What is Development?&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- when the words &quot;develop&quot; and &quot;development&quot; are used in the Scrum Guide, they refer to complex work and pertains to all activities needed to deliver a product increment (i.e. requirements analysis, design, coding, testing, docs, packaging, release, etc.)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Scrum Theory&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- based on empiricism -- rooted in experience, encounter with reality, observation, experimentation&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- pillars: Transparency, Inspection and Adaptation&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; inspect and adapt is a feedback loop, a cycle and is basically iterating the scientific method (there is a problem, you make observations, you come up with some hypothesis, you test it by experimenting i.e. trying out your hypothesis, you make conclusions, recommendations for future research/investigation, repeat)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; inspect and adapt is only effective with transparency&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; every Scrum event is an opportunity to inspect and adapt&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Side comment: I think these points are very important but are seldom emphasized in trainings. This is basically the Scrum thesis applied to software development: software development is a complex and adaptive process (as opposed to predictive; it is a blackbox/fundamentally uncertain because it is a creative process rather than well-defined/well-known; its first principles are unknown); to manage it and the risks that comes with it, we need an adaptive process, we need to constantly inspect and adapt, thus we need transparency, we need iterative and incremental development and not only that, we need the iterations to be short (to minimize risk); the product increment is basically an experiment and we learn, make conclusions, make adjustments, launch new experiments based on the stakeholders’, customers’ and market’s feedback).&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;&lt;a href=&quot;https://scrumorg-website-prod.s3.amazonaws.com/drupal/2018-05/ScrumValues-Tabloid.pdf&quot;&gt;Scrum Values&lt;/a&gt;&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- commitment, courage, focus, openness and respect&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- for you to reflect on; very important since as always values are the foundation where awesome things are built-on&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;(This was me attempting to relate/map Scrum values to Company values.)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; build for the long term (commitment, courage, focus)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; wear the customer&#39;s shoes (commitment, focus)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; our employees and their families matter (respect)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; humble (respect, openness)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; hungry (commitment, courage)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; have a point of view (courage, openness)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- values + pillars build trust; as we know, trust is very important -- organizational health rests on it&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Scrum Team&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- Product Owner&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; maximizes the value of the work done by the development team by clarifying and prioritizing product backlog items by value to the customer&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; can delegate but is ultimately accountable for the product backlog&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; there is only one PO per product backlog; the ultimate authority on &quot;what&quot; (but not &quot;how&quot;) to do&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;- Development Team&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; self-organizing, self-managing; decides on the &quot;how&quot;, how to turn product backlog into RELEASABLE increments&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; releasable is &lt;a href=&quot;https://agilepainrelief.com/notesfromatooluser/2017/05/definition-of-done-vs-user-stories-vs-acceptance-criteria.html#.WxmpQEiFM2w&quot;&gt;&quot;DONE&quot;&lt;/a&gt;; Scrum Team defines &quot;DONE&quot;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; cross-functional; has all the skills (requirements analysis, designing/architecting, coding, testing, documenting, etc.) to create a product increment&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;---&amp;gt; does that mean every team member must have all the skills? No, but broad competencies are desirable and acquiring those competencies/skills are encouraged since it promotes collaboration, mitigates risks among others (T-shaped developer)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; no titles, sub-teams regardless of work being performed, regardless of domains&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; development team members can have specializations, areas of expertise/focus; gaining deep skills/mastery over a specific area is also desirable and is encouraged&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; members may work on specific tasks but accountability belongs to the team as a whole; every team member is accountable for ensuring that the sprint goal is achieved&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Scrum Master&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; helps team understand and practice Scrum; to follow its rules, stay within the framework&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; serves development team by removing impediments&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; facilitates decision-making, coaches development team on self-organization and cross-functionality&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;--&amp;gt; helps find techniques to help team be more effective&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;===&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;&quot;Final&quot; Words&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Some weeks after I gave a &quot;talk&quot; to the team based on these notes, we decided to go over the Scrum Guide as a team. We spent an hour a week (or was it every two weeks) over several weeks going over the Scrum Guide, reading and re-reading it, discussing and reflecting on passages in it. We were conscious of how similar the format we adopted was to that of a Bible study (and we laughed at ourselves for it -- but we took the process and the learnings seriously nonetheless). Indeed, during those sessions, we took the Scrum Guide as our (Scrum) Bible. We also spent time, individually, taking and re-taking Scrum.org&#39;s open assessment. It did not take long until we were consistently getting 100% (the set of questions in the open assessment is quite limited) so a teammate asked me, &quot;What&#39;s the next step?&quot;. I did not have a ready answer for her at the time but I did come back with one a few sessions later: &quot;Scrum Patterns&quot;.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;(I hope to add more links to resources in the notes above at some future date.)&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/3102458266423470745/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2020/07/my-scrum-journey-in-beginning.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/3102458266423470745'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/3102458266423470745'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2020/07/my-scrum-journey-in-beginning.html' title='My Scrum Journey – In the Beginning'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-300172826019009678</id><published>2019-07-31T08:41:00.000-07:00</published><updated>2019-11-09T02:20:36.597-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Agile Methodologies"/><category scheme="http://www.blogger.com/atom/ns#" term="Software Engineering"/><title type='text'>Hello, Refactoring!</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
We often hear software developers use the word&amp;nbsp;&lt;strong&gt;refactor&lt;/strong&gt;&amp;nbsp;when talking about changing existing code. The word is used so loosely that doing just about any change is considered, incorrectly, a refactoring. Yes, to refactor means to change but not just any change; rather, refactoring entails a specific kind change to achieve a specific purpose.&lt;br /&gt;
&lt;h4 style=&quot;text-align: left;&quot;&gt;
&lt;b&gt;
..so what is refactoring exactly?&lt;/b&gt;&lt;/h4&gt;
&lt;h3 id=&quot;Hello,Refactoring!-..sowhatisrefactoringexactly?&quot;&gt;
&lt;o:p&gt;&lt;/o:p&gt;&lt;/h3&gt;
&quot;&lt;strong&gt;Refactoring is&lt;/strong&gt;&amp;nbsp;the process of&amp;nbsp;&lt;strong&gt;changing&lt;/strong&gt;&amp;nbsp;a software system in such a way&amp;nbsp;&lt;strong&gt;that&lt;/strong&gt;&amp;nbsp;it&amp;nbsp;&lt;strong&gt;does not&lt;/strong&gt;&amp;nbsp;&lt;strong&gt;alter&lt;/strong&gt;&amp;nbsp;the&amp;nbsp;&lt;strong&gt;external behavior&lt;/strong&gt;&amp;nbsp;of the code&amp;nbsp;&lt;strong&gt;yet improves&lt;/strong&gt;&amp;nbsp;its&amp;nbsp;&lt;strong&gt;internal structure&lt;/strong&gt;. It is a disciplined way to clean up code that minimizes the chances of introducing bugs. In essence when you refactor you are improving the design of the code after it has been written.&quot; -Martin Fowler&lt;br /&gt;
&lt;o:p&gt;&lt;/o:p&gt;&lt;br /&gt;
Or operationally, &quot;refactoring is the process of turning dirty code into clean code while keeping unit tests passing.&quot; - Idj&lt;br /&gt;
&lt;h4 style=&quot;text-align: left;&quot;&gt;
&lt;b&gt;But why refactor?&lt;/b&gt;&lt;/h4&gt;
&lt;h3 id=&quot;Hello,Refactoring!-Butwhyrefactor?&quot;&gt;
&lt;o:p&gt;&lt;/o:p&gt;&lt;/h3&gt;
(or what exactly does &quot;improves internal structure&quot; mean?)&lt;o:p&gt;&lt;/o:p&gt;&lt;br /&gt;
We refactor to:&lt;o:p&gt;&lt;/o:p&gt;&lt;br /&gt;
&lt;ul type=&quot;disc&quot;&gt;
&lt;li class=&quot;MsoNormal&quot;&gt;to keep code readable, modifiable and&amp;nbsp;&lt;a href=&quot;https://medium.freecodecamp.org/what-does-it-mean-when-code-is-easy-to-reason-about-4e6f63eb386f&quot;&gt;easy to reason about&lt;/a&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/li&gt;
&lt;li class=&quot;MsoNormal&quot;&gt;to pay&amp;nbsp;&lt;a href=&quot;https://towardsdatascience.com/refactoring-is-the-cure-for-technical-debt-but-only-if-you-take-it-9fd8cc42dd93&quot;&gt;technical debt&lt;/a&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/li&gt;
&lt;li class=&quot;MsoNormal&quot;&gt;to reduce&amp;nbsp;&lt;a href=&quot;https://www.quora.com/What-are-essential-and-accidental-complexity&quot;&gt;accidental complexity&lt;/a&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/li&gt;
&lt;li class=&quot;MsoNormal&quot;&gt;to go fast (by&amp;nbsp;&lt;a href=&quot;https://twitter.com/kentbeck/status/250733358307500032&quot;&gt;making change easy&lt;/a&gt;)&lt;o:p&gt;&lt;/o:p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 style=&quot;text-align: left;&quot;&gt;
That&#39;s all well and good but how do we know when to refactor?&lt;/h4&gt;
&lt;h3 id=&quot;Hello,Refactoring!-That&#39;sallwellandgoodbuthowdoweknowwhentorefactor?&quot;&gt;
&lt;o:p&gt;&lt;/o:p&gt;&lt;/h3&gt;
Easy, train and use your sense of&amp;nbsp;&lt;a href=&quot;https://martinfowler.com/bliki/CodeSmell.html&quot;&gt;code smell&lt;/a&gt;. The more you use it, the better it gets. Here are two common code smells:&lt;o:p&gt;&lt;/o:p&gt;&lt;br /&gt;
&lt;ul type=&quot;disc&quot;&gt;
&lt;li class=&quot;MsoNormal&quot;&gt;&lt;a href=&quot;https://refactoring.guru/smells/long-method&quot;&gt;Long method&lt;/a&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/li&gt;
&lt;li class=&quot;MsoNormal&quot;&gt;&lt;a href=&quot;https://refactoring.guru/smells/feature-envy&quot;&gt;Feature envy&lt;/a&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/li&gt;
&lt;/ul&gt;
Find more&amp;nbsp;&lt;a href=&quot;https://refactoring.guru/refactoring/smells&quot;&gt;here&lt;/a&gt;.&lt;br /&gt;
&lt;h4 style=&quot;text-align: left;&quot;&gt;
Okay, seems legit. We want to learn. What do we do?&amp;nbsp;&lt;/h4&gt;
&lt;h3 id=&quot;Hello,Refactoring!-Okay,seemslegit.Wewanttolearn.Whatdowedo?&quot;&gt;
&lt;o:p&gt;&lt;/o:p&gt;&lt;/h3&gt;
Good. Start with two of the most common refactoring techniques:&lt;o:p&gt;&lt;/o:p&gt;&lt;br /&gt;
&lt;ul type=&quot;disc&quot;&gt;
&lt;li class=&quot;MsoNormal&quot;&gt;&lt;a href=&quot;https://sourcemaking.com/refactoring/extract-method&quot;&gt;Extract method&lt;/a&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/li&gt;
&lt;li class=&quot;MsoNormal&quot;&gt;&lt;a href=&quot;https://sourcemaking.com/refactoring/move-method&quot;&gt;Move method&lt;/a&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/li&gt;
&lt;/ul&gt;
Check out more&amp;nbsp;&lt;a href=&quot;https://sourcemaking.com/refactoring/refactorings&quot;&gt;here&lt;/a&gt;. Do exercises like&amp;nbsp;&lt;a href=&quot;https://www.cs.virginia.edu/~horton/cs494/s05/slides/lab-exercise-refactoring.htm&quot;&gt;this&lt;/a&gt;.&lt;o:p&gt;&lt;/o:p&gt;&lt;br /&gt;
But most importantly, read the&amp;nbsp;&lt;a href=&quot;https://www.csie.ntu.edu.tw/~r95004/Refactoring_improving_the_design_of_existing_code.pdf&quot;&gt;bible&lt;/a&gt;. Practice what you&#39;ve read. Spread the word.&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/300172826019009678/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2019/07/hello-refactoring.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/300172826019009678'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/300172826019009678'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2019/07/hello-refactoring.html' title='Hello, Refactoring!'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-1657595432677041758</id><published>2019-06-27T11:23:00.000-07:00</published><updated>2019-11-09T02:27:16.940-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Agile Methodologies"/><category scheme="http://www.blogger.com/atom/ns#" term="Excellence"/><category scheme="http://www.blogger.com/atom/ns#" term="Software Engineering"/><title type='text'>Journey to Mastery</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;div&gt;
&lt;i&gt;The following is the resignation letter I am going to send to my manager in the next couple of days.&lt;/i&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Hi ***,&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Please consider this as my formal notice of resignation effective July 31, 2019. My last day of work will be July 30, 2019.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I have been with [company] for over two years now and for the most part, it was a rewarding experience -- especially my stint as the lead of the [team] and for this, I am grateful.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
In my years as a developer, I have seen and been with teams in many organizations and I can say with pride and confidence that this team embodies the spirit of agile the closest -- self-organizing, cross-functional and always seeking to improve. Of course, the journey to mastery never ends (or as Kent Beck puts it, perfect is a verb, not an adjective). It&#39;s non-linear and context-dependent. The struggle to overcome our weaknesses and reinforce our strengths is constant. It is real. To get side-tracked, make mistakes, fall behind or fail is inevitable. At the end of the day, it&#39;s the motivation of the people in the team that carries them through the errors and failures into the next level. And from what I&#39;ve seen, I have no doubt that the [team] has what it takes. It will do well with or without me.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Regards,&lt;/div&gt;
&lt;div&gt;
Ronald&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
---------------------------------------------------------------------------&lt;/div&gt;
&lt;div&gt;
&lt;i&gt;I decided the above was too dramatic. So, here&#39;s what I actually sent.&lt;/i&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Please consider this as my formal notice of resignation effective July 31, 2019. My last day of work will be July 30, 2019.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I have been with [company] for over two years now and as a whole, it was a rewarding experience; especially my stint as the lead of the [team], for which I am most grateful.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
In my years as a developer, I have seen and been with teams in many organizations and it is not too much of a stretch for me to say that the [team] is the best (if not in actual, then definitely, in potential). It strives to be agile and lean. It is self-organizing, autonomous and cross-functional. The journey to mastery is a struggle but given time and opportunity, I have no doubt that the Collection team will get there with or without me. I hope I get the chance to work with such a team again in the future.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/1657595432677041758/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2019/06/journey-to-mastery.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/1657595432677041758'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/1657595432677041758'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2019/06/journey-to-mastery.html' title='Journey to Mastery'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-996779445054611476</id><published>2019-06-27T11:16:00.000-07:00</published><updated>2019-06-27T11:31:27.079-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Excellence"/><category scheme="http://www.blogger.com/atom/ns#" term="Human Dynamics"/><category scheme="http://www.blogger.com/atom/ns#" term="Learning"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Building a Culture of Organizational Excellence</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;i&gt;The following is an e-mail I wrote to my managers about 4 years ago when they asked for feedback/ideas on the &quot;cross-pollination&quot; initiative they were planning to launch.&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
Hi Scott, Joel, Alona, Jenny,&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
This is several weeks late but I hope it could still be of some value.&amp;nbsp;I have considered going directly to&amp;nbsp;my&amp;nbsp;suggestions/recommendations but I thought it may be worthwhile to also share how I got to them. (This is as much an attempt to organize my thoughts on &quot;cross pollination&quot;, learning and knowledge-sharing as it is an attempt to synthesize and share&amp;nbsp;ideas from books and articles I&#39;ve read recently and not so recently so I hope its tone and length don&#39;t turn you off.)&lt;br /&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Personally, I think &quot;cross pollination&quot; is a great idea but, as&amp;nbsp;is probably obvious to&amp;nbsp;everyone,&amp;nbsp;doing it effectively is quite daunting&amp;nbsp;because there isn&#39;t a simple, straight-forward formula or a sure-fire method to&amp;nbsp;guarantee its success (i.e. that the desired outcome is realized -- a high&amp;nbsp;number of&amp;nbsp;engineers with sufficient retained knowledge&amp;nbsp;to competently&amp;nbsp;work&amp;nbsp;on multiple products.)&amp;nbsp;This, I believe, is because it all boils&amp;nbsp;down to the people or the engineers involved who have varying skills, motivations and capabilities. (The variance is of such magnitude that, according to this&amp;nbsp;&lt;a href=&quot;http://www.hrma.ca/wp-content/uploads/2012/11/rb-the-best-and-the-rest.pdf&quot; rel=&quot;nofollow&quot; style=&quot;color: #196ad4;&quot; target=&quot;_blank&quot;&gt;study&lt;/a&gt;&amp;nbsp;which is the basis of this&amp;nbsp;&lt;a href=&quot;http://www.forbes.com/sites/joshbersin/2014/02/19/the-myth-of-the-bell-curve-look-for-the-hyper-performers/&quot; rel=&quot;nofollow&quot; style=&quot;color: #196ad4;&quot; target=&quot;_blank&quot;&gt;article&lt;/a&gt;,&amp;nbsp;the traditional normal or&amp;nbsp;bell curve, which SeaChange continue to use, is ill-suited for characterizing performance distributions in organizations and that the so called power law or curve, which seems to pop up in various areas in human dynamics,&amp;nbsp;is more appropriate.) As such, I&amp;nbsp;consider the following to be key to&amp;nbsp;doing &quot;cross pollination&quot; in our context&amp;nbsp;effectively:&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
1. Willingness of engineers to learn&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
2. Their ability to learn quickly&lt;/div&gt;
&lt;div&gt;
3. Their&amp;nbsp;problem-solving,&amp;nbsp;analytical &amp;amp; critical thinking skills&lt;/div&gt;
&lt;div&gt;
4. Their&amp;nbsp;sense of (collective) ownership i.e. doing whatever it takes to get the&amp;nbsp;tasks done&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
5. Hiring the right people to begin with&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
6. Keeping them motivated to excel&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
To a significant degree, items 1 - 4, particularly&amp;nbsp;2 &amp;amp; 3,&amp;nbsp;are pre-determined (which is&amp;nbsp;why I think the importance of&amp;nbsp;5 &amp;amp; 6 cannot be over&amp;nbsp;emphasized). Some are just innately predisposed, while others&amp;nbsp;are not.&amp;nbsp;(Furthermore, they&amp;nbsp;are hard to measure. How&amp;nbsp;can an engineer&#39;s willingness to learn or whether or not he/she has good problem-solving skills be measured.&amp;nbsp;I doubt if any single metric can accurately capture any of these &quot;competencies&quot;&amp;nbsp;but my hope is that there is an identifiable set of KPIs that can effectively measure, if not the &quot;competencies&quot; directly then, the results they are expected to&amp;nbsp;produce.)&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
However, regardless of innate predispositions, I believe that&amp;nbsp;all four&amp;nbsp;can also be acquired or learned, at least to a certain extent, and that the&amp;nbsp;right&amp;nbsp;organizational culture (shared values, beliefs, mindset &amp;amp; norms)&amp;nbsp;is key to acquiring them (over,&amp;nbsp;say, formal training or rigid processes because these &quot;competencies&quot; like many others require&amp;nbsp;&lt;a href=&quot;https://en.wikipedia.org/wiki/Tacit_knowledge&quot; rel=&quot;nofollow&quot; style=&quot;color: #196ad4;&quot; target=&quot;_blank&quot;&gt;tacit&lt;/a&gt;&amp;nbsp;knowledge that by nature is&amp;nbsp;difficult, if not impossible, to codify.)&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Thus, to be successful (with &quot;cross pollination&quot;), I believe we need to create a culture where 1)&amp;nbsp;excellence and learning are valued, 2)&amp;nbsp;collaboration and knowledge-sharing are the norm, 3)&amp;nbsp;challenging/questioning the status quo is encouraged, if not expected, and 4) every team member feels&amp;nbsp;collectively responsible for each of the team&#39;s deliverables (or more generally, for the success or failure of the entire organization.) Moreover, I believe that if we are to succeed (in creating such a culture), we ought to&amp;nbsp;expect the process/journey&amp;nbsp;to be messy, difficult, protracted and&amp;nbsp;iterative, fraught&amp;nbsp;with errors and failed experiments (that we nonetheless have to make)&amp;nbsp;&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
I realize&amp;nbsp;that 1) although these are lofty ideals, they are rather abstract -- what we need are concrete practices; 2) they cannot be achieved overnight or at all, without focused, coordinated effort and constant follow-through; and 3) ultimately, it is the &quot;plumbing&quot; and not the &quot;poetry&quot; that counts -- it&#39;s going to be the nitty-gritty, day-to-day&amp;nbsp;implementation that determines our success or failure.&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;div&gt;
So in this vein,&amp;nbsp;here&#39;s my attempt at&amp;nbsp;some raw but&amp;nbsp;concrete (-enough, I hope) recommendations:&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;b&gt;1. Institutionalize knowledge sharing&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
&amp;nbsp;A. Regular (monthly?) half-a-day(?) sessions where engineers share:&lt;/div&gt;
&lt;div&gt;
a. What their teams are currently doing and why to other teams&lt;/div&gt;
&lt;div&gt;
b. Challenging problems solved recently and how&lt;/div&gt;
c. Demo new product features or share lessons learned from last sprint&lt;br /&gt;
&lt;div&gt;
e.&amp;nbsp;Other interesting topics they found useful and think will be useful or at least, of interest to other teams (e.g.&amp;nbsp;Java GC, Cassandra internals, performance tuning tools, etc.)&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
-&amp;nbsp;As introduction/first topic, engineers could discuss/refresh the overview/architecture of products they sustain/develop and how these various products fit together.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
-&amp;nbsp;I envision this to be&amp;nbsp;relaxed and&amp;nbsp;informal (more akin to a discussion over dinner&amp;nbsp;rather than a formal training)&amp;nbsp;where engineers can freely discuss and ask questions&amp;nbsp;even remotely tangential to the topic at hand.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
-&amp;nbsp;The point being&amp;nbsp;to create linkages or open channels where knowledge can diffuse across teams and product &quot;silos&quot; as well as&amp;nbsp;reduce the learning curve for engineers that will be &quot;cross-pollinated&quot;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
- Can&#39;t be called &quot;knowlegde-sharing sessions&quot;; catchy name needed&amp;nbsp;&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&amp;nbsp;B. Augmented Scrum&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
- Augment or even just re-focus the 3 traditional scrum questions of &quot;what did i do yesterday?&quot;, &quot;what will i do today?&quot;, &quot;what issues are blocking me?&quot; with &quot;who did i help yesterday?&quot;, &quot;what new concept or technique did i learn yesterday?&quot;, &quot;who will i help today?&quot; and &quot;what do i need/want to learn today?&quot;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
- The point is for engineers to be always conscious of learning and knowledge-sharing/collaboration as well as recognize their value in relation to their tasks.&amp;nbsp;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
- I see cross-pollinated members (or &quot;cross-pollinees&quot;) as primary players and beneficiaries of all these &quot;learning and helping&quot;.&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&amp;nbsp;C. Re-vitalize the Wiki&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
- I believe our wiki has some very valuable content but is poorly organized. There ought to be a conscious effort at improving its structure and links (between articles/entries even beyond product &quot;silos&quot;) and that effort should be considered a &quot;real&quot; task (i.e. managers should recognize/promote that it&#39;s worth allocating putting hours into) rather than just a side-task or a filler. Perhaps, techpubs can also help out or even lead this undertaking (i.e. improving organization and linkages of wiki pages).&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
- Creating wiki pages should be made an essential/integral part of an engineer&#39;s workflow, again, rather than just being an after-though or an add-on task or worse a distraction e.g. make it an expected artifact or better, another channel where engineers discuss ideas.&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
- Managers should start using the wiki too; for meeting minutes, documenting plans, updates, ideas or whatnot &amp;nbsp;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
- Naturally, &quot;cross-pollinees&quot; will once again be primary drivers here since they will be doing a lot of learning and should utilize the wiki to take note and organize what they&#39;ve learned.&amp;nbsp;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&amp;nbsp;D. Debriefing &quot;Cross-pollinees&quot;&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
- When cross-pollinated members return to his/her original team or transfer to a new team, there must a mechanism/venue/expectation for him/her to share what he/she learned from the team prior, even if it&#39;s just an overview of the other team&#39;s product or the detailed design of a some very specific component.&lt;/div&gt;
&lt;div style=&quot;background-color: white; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 16px;&quot;&gt;
&lt;br /&gt;
&lt;div&gt;
&lt;b&gt;&lt;br /&gt;&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
&lt;b&gt;2. Encourage, or even force, collaboration&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
- Design/create user stories in a way that encourage collaboration or even manufacture, instead of avoiding, inter-dependent stories that force&amp;nbsp;engineers within and across teams to collaborate so engineers&amp;nbsp;could learn from each other&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
- Move away from the mindset that individual engineers are allocated to specific stories/tasks as it naturally fragments the team (with individual engineers pre-occupied with his and only his tasks), instead &quot;assigned&quot; engineers should be seen as leads or primary movers of stories that are collectively owned by the team; the entire team is expected or even required to contribute. Naturally, this implies that a team can&#39;t have too many members or too diverse or too many stories at once (if this is the case, then, despite appearances, there isn&#39;t actually one but multiple teams.)&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
- Mentoring/coaching others should not&amp;nbsp;be treated just as a side task to be undertaken when one&#39;s schedule allows (and thus something unaccounted and hence, seen as&amp;nbsp;a burden), but a task and a goal in itself with its &quot;cost&quot; (in hours or whatever) and &quot;returns&quot; fully recognized by managers and the team. In other words, it must be made (or made known explicitly to the team that it is) an expected activity/task worth putting hours into and a value in itself.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
- A&amp;nbsp;&quot;cross-pollinee&quot;&amp;nbsp;should be&amp;nbsp;assigned, together with an&amp;nbsp;experienced engineer, to an&amp;nbsp;important story in&amp;nbsp;the current sprint,&amp;nbsp;preferably one that&amp;nbsp;requires learning a significant&amp;nbsp;breadth of product knowledge. This setup, especially because the story is important, makes collaboration imperative and in the interest not just of the &quot;cross-pollinee&quot; but of the entire team (because it can potentially make or break the sprint). It is therefore imperative to clarify and constantly re-iterate that though only two engineers are assigned to the story, it is the collective responsibility of the entire team.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;b&gt;3. Supplement story planning/commit meetings with design and strategy meetings&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
- In practice, the &quot;formal&quot;&amp;nbsp;story planning has&amp;nbsp;been reduced to identifying stories/tasks, high-level estimation and resource allocation i.e. assigning the stories and scheduling release dates.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
- A deeper-level discussion doesn&#39;t really happen and understandably so, because the information to facilitate such discussions are, more often than not, &amp;nbsp;not yet available at that time and also because during commit meetings coming up with dates and schedules are the primary focus/pre-occupation. (I&#39;m not looking for implementation-level detailed discussion but definitely something deeper than the usual high-level discussion during planning.)&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
- I believe the best time for such discussions to happen is during follow-on meetings at the point when an engineer is ready to design a solution or come up with a testing strategy.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
- This should also provide a venue for analytical/critical discussions that are too long to be accommodated during scrums but too valuable to let slip.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
- (And, even as I write this, it seems off to me or it seems to me that the order is somehow backwards -- that estimates and commits come ahead of these more &quot;deeper-level&quot; discussions.)&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;b&gt;4. Reward excellence&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
- Make&amp;nbsp;the process of selecting awardees more objective &amp;amp; transparent; to&amp;nbsp;be truly fair,&amp;nbsp;reward base on&amp;nbsp;merit, instead of trying to spread bonuses &quot;to be fair.&quot;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
- Identify&amp;nbsp;KPIs&amp;nbsp;and track individual and team performance based on these&amp;nbsp;KPIs; the KPIs themselves need to be carefully selected and under constant review; also, extreme&amp;nbsp;care must be taken so the identified KPIs do not result to the opposite of the desired behavior i.e. engineers becoming too cautious or taking too much risk (and cutting corners as a result) or worse, &quot;gaming&quot; the system (to get high marks on KPIs without actually delivering or even eroding value.)&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
- Move&amp;nbsp;away from the normal-curve based annual&amp;nbsp;raises; treat performance evaluations as a re-hiring process (e.g. instead of &quot;engineer X got a rating of Y, that puts him/her on the top so-and-so % and so he/she gets Z percent increase&quot;, why not &quot;engineer X adds this much value to the team, losing him/her would be a pain; in our industry&#39;s job market, he/she would probably get, and so deserves a salary of, A (and not some percentage value based on his current pay.)&quot;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
- Come-up with team-centric incentives to reward excellent,highly-collaborative teams; perhaps instead of, or better, on top of individual bonuses, there could be team bonuses; there ought to be some level of &quot;rationalization&quot; or &quot;normalization&quot; though, since not all teams get equal opportunities to &quot;shine&quot;.&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Thank you for reading all the way through.&lt;/div&gt;
&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;span style=&quot;background-color: white; font-family: &amp;quot;calibri&amp;quot; , &amp;quot;arial&amp;quot; , &amp;quot;helvetica&amp;quot; , sans-serif; font-size: 16px;&quot;&gt;&lt;span style=&quot;color: #888888;&quot;&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;div&gt;
-Ronald&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/996779445054611476/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2019/06/building-culture-of-organizational.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/996779445054611476'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/996779445054611476'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2019/06/building-culture-of-organizational.html' title='Building a Culture of Organizational Excellence'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-4455453140374758118</id><published>2018-06-23T09:10:00.001-07:00</published><updated>2018-08-08T12:54:28.121-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Human Dynamics"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Effectivity of Selection Methods as Predictor of Job Performance</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;div class=&quot;wiki-content&quot; id=&quot;main-content&quot; style=&quot;background-color: white; color: #333333; font-family: Arial, sans-serif; font-size: 14px; margin: 0px; padding: 0px;&quot;&gt;
&lt;div style=&quot;padding: 0px;&quot;&gt;
Most of the articles I&#39;ve read that compare selection methods as predictor of job performance eventually (because some articles cite articles that then cite the study) cites this&amp;nbsp;&lt;a class=&quot;external-link&quot; href=&quot;http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.172.1733&amp;amp;rep=rep1&amp;amp;type=pdf&quot; rel=&quot;nofollow&quot; style=&quot;color: #662d91; text-decoration-line: none;&quot; target=&quot;_blank&quot;&gt;study&lt;/a&gt;. Looking it up in Google Scholar reveals that it has been cited by over 4500 studies (note not merely articles but studies published in scientific journals). This tells me that the study is credible.&lt;/div&gt;
&lt;div style=&quot;margin-top: 10px; padding: 0px;&quot;&gt;
The study itself is a&amp;nbsp;&lt;a class=&quot;external-link&quot; href=&quot;https://en.wikipedia.org/wiki/Meta-analysis&quot; rel=&quot;nofollow&quot; style=&quot;color: #662d91; text-decoration-line: none;&quot; target=&quot;_blank&quot;&gt;meta-analysis&lt;/a&gt;&amp;nbsp;of research studies conducted in the past 85 years (until 1998). The study and its findings is not without its critics. For instance, this&amp;nbsp;&lt;a class=&quot;external-link&quot; href=&quot;https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4557354/&quot; rel=&quot;nofollow&quot; style=&quot;color: #662d91; text-decoration-line: none;&quot; target=&quot;_blank&quot;&gt;study&lt;/a&gt;&amp;nbsp;questions the validity of its conclusions given the uncertain quality of the original data of some studies included in the meta-analysis. However, I find that the criticisms (of that particular study) apply equally to the different selection methods. So, as far as the organizations&#39; practical problem of choosing selection methods is concerned, I believe the conclusions in this (and a recent version) are still the best we&#39;ve got (in terms of being backed by empirical data and scientific rigor.)&amp;nbsp;&lt;/div&gt;
&lt;div style=&quot;margin-top: 10px; padding: 0px;&quot;&gt;
A&amp;nbsp;&lt;a class=&quot;external-link&quot; href=&quot;https://www.researchgate.net/publication/309203898_The_Validity_and_Utility_of_Selection_Methods_in_Personnel_Psychology_Practical_and_Theoretical_Implications_of_100_Years_of_Research_Findings&quot; rel=&quot;nofollow&quot; style=&quot;color: #662d91; text-decoration-line: none;&quot; target=&quot;_blank&quot;&gt;working paper&lt;/a&gt;&amp;nbsp;that updates the study was made available in 2016. It expands the meta-analysis to cover 100 years (until 2016) of research findings. The main findings and their practical implications remain the same but some findings differ.&lt;/div&gt;
&lt;div style=&quot;margin-top: 10px; padding: 0px;&quot;&gt;
Both the original and the updated paper found&amp;nbsp;&lt;strong&gt;tests of&lt;/strong&gt;&amp;nbsp;&lt;strong&gt;general mental ability (GMA)&lt;/strong&gt;&amp;nbsp;to be a better predictor of job performance than either structured and unstructured interviews. In fact, in the updated paper it was found to be&lt;strong&gt;&amp;nbsp;the single most effective predictor of job performance&lt;/strong&gt;&amp;nbsp;(in the original it was a close second to work sample tests). Moreover, in both paper, GMA was also found to be&amp;nbsp;&lt;strong&gt;the single most effective predictor of job-related learning&lt;/strong&gt;&amp;nbsp;(i.e. amount learned on-the-job and in trainings).&lt;/div&gt;
&lt;div style=&quot;margin-top: 10px; padding: 0px;&quot;&gt;
Both papers also found that when combined with GMA,&lt;strong&gt;&amp;nbsp;integrity tests&lt;/strong&gt;&amp;nbsp;yielded the highest incremental improvement over GMA alone as predictor of job performance followed closely by&amp;nbsp;&lt;strong&gt;structured interviews&lt;/strong&gt;.&lt;/div&gt;
&lt;div style=&quot;margin-top: 10px; padding: 0px;&quot;&gt;
My take on these is pretty clear. Let&#39;s do GMA tests. &lt;a href=&quot;https://www.fastcompany.com/40579524/what-if-we-killed-the-job-interview&quot; target=&quot;_blank&quot;&gt;Doing away with interviews altogether&lt;/a&gt; is not unjustified. If we must do interviews, let&#39;s do structured interviews. The rest of the selection methods are either too costly (in terms of effort and resources required like work samples) or just really poor predictors (reference checks, years of job experience, person-organization fit, personality tests).&lt;/div&gt;
&lt;/div&gt;
&lt;div id=&quot;likes-and-labels-container&quot; style=&quot;background-color: white; clear: both; color: #333333; font-family: Arial, sans-serif; font-size: 14px; margin: 10px 0px; overflow: hidden; padding: 10px 0px;&quot;&gt;
&lt;div class=&quot;no-print&quot; id=&quot;likes-section&quot; style=&quot;float: left; font-size: 13px; margin: 0px; padding: 0px; width: 329.508px;&quot;&gt;
&lt;a class=&quot;like-button&quot; href=&quot;https://ice.itrsgroup.com/pages/viewpage.action?spaceKey=dev&amp;amp;title=Effectivity+of+selection+methods+as+predictor+of+job+performance&quot; style=&quot;color: #662d91; display: block; float: left; text-decoration-line: none;&quot;&gt;&lt;span class=&quot;aui-icon aui-icon-small aui-iconfont-like&quot; style=&quot;background-position: 0px 0px; background-repeat: no-repeat; border: none; color: #707070; display: inline-block; height: 16px; line-height: 0; margin: 0px; padding: 0px; position: relative; text-indent: -999em; vertical-align: text-top; width: 16px;&quot;&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/4455453140374758118/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2018/06/effectivity-of-selection-methods-as.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/4455453140374758118'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/4455453140374758118'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2018/06/effectivity-of-selection-methods-as.html' title='Effectivity of Selection Methods as Predictor of Job Performance'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-4140628793810472941</id><published>2018-06-09T08:00:00.001-07:00</published><updated>2018-06-09T08:04:46.672-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Agile Methodologies"/><category scheme="http://www.blogger.com/atom/ns#" term="Software Engineering"/><category scheme="http://www.blogger.com/atom/ns#" term="Technology Management"/><title type='text'>Software Development as an Empirical Process</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;If a process can be fully defined, with all things known about it so that it can be
designed and run repeatably with predictable results, it is known as a defined
process, and it can be subjected to automation. If all things about a process aren&#39;t
fully known -- only what generally happens when you mix these inputs and what
to measure and control to get the desired output -- these are called empirical
processes.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;A defined process is predictable; it performs the same every time. An empirical
process requires close watching and control, with frequent intervention. It is
chaotic and unrepeatable, requiring constant measurement to ensure the desired
result.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;Models of empirical processes are derived by categorizing observed inputs and
outputs and defining the controls that cause them to occur within prescribed
bounds. Empirical process modeling involves constructing a process model
strictly from experimentally obtained input/output data, with no recourse to any
laws concerning the fundamental nature and properties of the system. No a priori
knowledge about the process is necessary; a process is treated like a black box.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;[S]cientists inspected the systems development process. They concluded that
many of the processes, rather than being repeatable, defined, and predictable,
were unpredictable and unrepeatable. With that, the scientists explained the
difference between defined processes and empirical processes.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;The scientists stated, &#39;We are most amazed that your industry treats these illformed
processes as defined, and performs them without controls despite their
irregular nature. If chemical processes that we don&#39;t understand completely were
handled in the same way, we would get very unpredictable results.&#39;&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;The scientists recommended -- since our business is an empirical process -- that
we use measurements and controls, as done elsewhere in the physical world. The
scientists provided the concepts of defined and empirical processes .. and they
told us that we needed controls to manage the empirical systems development
process.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;i&gt;Controlled-Chaos Software Development.&amp;nbsp;&lt;/i&gt;&lt;br /&gt;
Retrieved on June 9, 2018 from&lt;br /&gt;
&lt;a href=&quot;http://static1.1.sqspcdn.com/static/f/447037/6486035/1270926469320/Controlled-Chaos+Software+Development.pdf?token=NdnSJ23pP9yBLAfDSHQHZqIOc2U%3D&quot;&gt;http://static1.1.sqspcdn.com/static/f/447037/6486035/1270926469320/Controlled-Chaos+Software+Development.pdf?token=NdnSJ23pP9yBLAfDSHQHZqIOc2U%3D&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/4140628793810472941/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2018/06/software-development-as-empirical.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/4140628793810472941'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/4140628793810472941'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2018/06/software-development-as-empirical.html' title='Software Development as an Empirical Process'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-8904764064465095979</id><published>2017-04-22T12:14:00.000-07:00</published><updated>2017-04-22T12:16:50.937-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Agile Methodologies"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Agile Management</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;[O]ne of the biggest wastes these days..is waste of talent, that a lot of people in the organization are capable of being far more innovative than they’re ever being asked to do.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;They don’t want to be 10 layers below a CEO just executing what some middle manager is telling them they should be doing. They want to be involved in important projects, feeling like a team, and feeling like they’re making important contributions.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;[I]f you create a great team, they are capable of doing far more than most management teams think they are capable of doing today.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;[T]he biggest challenge for traditional management– who wants to have a command control, hierarchical mode of working with linear timelines and dates and arbitrary commitments that are forced on the workers– this is like a total shift, because coming out of the lean context, lean is a pull system.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;[I]t means that a senior executive has to stop giving command and control orders to what a team should be doing. And they’ve got to stop fragmenting their best workers over so many projects. It is not uncommon for me to run into very capable senior executives who have no more than 5% or 10% of their time allocated to myriad projects, and that’s just catastrophic.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;[Y]ou [have to] understand the dangers of multitasking, what that does to the quality of the products, to the morale of the workers, to the productivity of the teams, multi-tasking is a killer. So we have to teach executives that it is not a good thing to fragment the workers. It’s not a good thing to overturn their decisions. It’s not a good thing to put 50 people on a team as opposed to nine people on a team.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;[G]ive the senior executives enough of an education that they don’t unintentionally kill the effort, that they don’t overturn their decisions, that they don’t interfere, that they don’t pull team members off partway through the project.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;i&gt;Understanding Agile Management. &lt;/i&gt;(2016). Harvard Business Review. Retrieved on April 23, 2017 from&amp;nbsp;&lt;a href=&quot;https://hbr.org/ideacast/2016/04/understanding-agile-management&quot;&gt;https://hbr.org/ideacast/2016/04/understanding-agile-management&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/8904764064465095979/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/04/agile-management.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/8904764064465095979'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/8904764064465095979'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/04/agile-management.html' title='Agile Management'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-5974089403450276241</id><published>2017-04-21T04:10:00.001-07:00</published><updated>2017-04-21T04:15:38.877-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Human Dynamics"/><category scheme="http://www.blogger.com/atom/ns#" term="Learning"/><title type='text'>Technical Interviewing is a Broken Process</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;After drawing on data from thousands of technical interviews, it’s become clear to us that technical interviewing is a process whose results are nondeterministic and often arbitrary. We believe that technical interviewing is a broken process...&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;[C]oming up with interview questions and processes is really hard, so despite their differing needs, smaller companies often take their cues from the larger players, not realizing that companies like Google are successful at hiring because the work they do attracts an assembly line of smart, capable people... and that their success at hiring is often despite their hiring process and not because of it. So you end up with a de facto interviewing cargo cult, where smaller players blindly mimic the actions of their large counterparts and blindly hope for the same results.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;The worst part is that these results may not even be repeatable…&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;After looking at thousands of interviews.., we’ve discovered something alarming: interviewee performance from interview to interview varied quite a bit, even for people with a high average performance.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;At the end of the day, because technical interviewing is indeed a game, like all games, it takes practice to improve. However, unless you’ve been socialized to expect and be prepared for the game-like aspect of the experience, it’s not something that you can necessarily intuit. And if you go into your interviews expecting them to be indicative of your aptitude at the job, which is, at the outset, not an unreasonable assumption, you will be crushed the first time you crash and burn. But the process isn’t a great or predictable indicator of your aptitude. And on top of that, you likely can’t tell how you’re doing even when you do well.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;A noisy, non-deterministic interview process does no favors to either candidates or companies. Both end up expending a lot more effort to get a lot less signal than they ought, and in a climate where software engineers are at such a premium, noisy interviews only serve to exacerbate the problem.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;[I]n the absence of a radical shift in how we vet technical ability, we’ve learned that drawing on aggregate performance is much more meaningful than a making such an important decision based on one single, arbitrary interview. Not only can aggregate performance help correct for an uncharacteristically poor performance, but it can also weed out people who eventually do well in an interview by chance or those who, over time, simply up and memorize &lt;i&gt;Cracking the Coding Interview&lt;/i&gt;. [E]ven after just a handful of interviews, we have a much better picture of what someone is capable of and where they stack up than a single company would after a single interview, and aggregate data tells a much more compelling, repeatable story than one, arbitrary data point.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Lerner, Aline. (2016), &lt;i&gt;You can&#39;t fix diversity in tech without fixing the technical interview&lt;/i&gt;. Interviewing.io. Retrieved on April 21, 2017 from&amp;nbsp;&lt;a href=&quot;http://blog.interviewing.io/you-cant-fix-diversity-in-tech-without-fixing-the-technical-interview/&quot;&gt;http://blog.interviewing.io/you-cant-fix-diversity-in-tech-without-fixing-the-technical-interview/&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Lerner, Aline. (2016),&amp;nbsp;&lt;i&gt;After a lot more data, technical interview performance is kind of arbitrary&lt;/i&gt;. Interviewing.io. Retrieved on April 21, 2017 from&amp;nbsp;&lt;a href=&quot;http://blog.interviewing.io/you-cant-fix-diversity-in-tech-without-fixing-the-technical-interview/&quot;&gt;http://blog.interviewing.io/you-cant-fix-diversity-in-tech-without-fixing-the-technical-interview/&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/5974089403450276241/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/04/technical-interviewing-is-broken-process.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/5974089403450276241'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/5974089403450276241'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/04/technical-interviewing-is-broken-process.html' title='Technical Interviewing is a Broken Process'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-4014965429763952588</id><published>2017-04-20T07:43:00.002-07:00</published><updated>2017-04-20T07:43:50.586-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Innovation"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Collaboration, Alignment and Distributed Decision-Making for Product Success</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;[S]iloed product and technology teams lead to missed opportunities, project delays or sometimes straight-up project failure.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;When such teams are not aligned in process and execution, differences in vision and capability are not recognized until time, money and brainpower have already been spent. That’s far too late to discover they don’t see eye to eye on a product’s feasibility or potential value to the company.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;Very early on in the innovation process, product managers must partner with technical experts who can provide a real-world perspective into the scope of a proposed new product.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;Innovative companies must place a strong priority on distributed decision making whereby many people with skills in different areas are employed to come to a consensus on which products to pursue and how to proceed. Be forewarned that such processes require highly skilled technical personnel and a clear plan for how the group will come to actionable decisions. Establishing a highly competent product owner who can serve as a linchpin in the product lifecycle, removing organizational gaps and ensuring a more comprehensive product vision is realized, can help facilitate that process.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;i&gt;Digital Innovation Best Practices: Early Partnerships Ensure Success&lt;/i&gt;. (2017). Magenic. Retrieved on April 20, 2017 from&amp;nbsp;&lt;a href=&quot;https://magenic.com/media/2247/wp_mgnc-digital-innovation-best-practices-early-partnerships.pdf&quot;&gt;https://magenic.com/media/2247/wp_mgnc-digital-innovation-best-practices-early-partnerships.pdf&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/4014965429763952588/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/04/collaboration-alignment-and-distributed.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/4014965429763952588'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/4014965429763952588'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/04/collaboration-alignment-and-distributed.html' title='Collaboration, Alignment and Distributed Decision-Making for Product Success'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-266671905292959275</id><published>2017-04-07T01:42:00.000-07:00</published><updated>2017-04-07T08:00:57.214-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Agile Methodologies"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Agile Model of HR</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;[A]gile principles are key to supporting the kind of continuous learning, continuous talent acquisition, and transparent processes that enable organizations to attract, develop, and engage talent in the twenty-first century.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;The &#39;Agile Model of HR&#39; states that human resources&#39; job is not just to implement controls and standards, and drive execution—but rather to facilitate and improve organizational agility. This changes HR&#39;s mission and focus. Driving agility means driving programs that create adaptability, innovation, collaboration, and speed.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;[A]gile HR strategies include:&lt;br /&gt;
&lt;br /&gt;
&lt;ul style=&quot;text-align: left;&quot;&gt;
&lt;li&gt;Training leaders at all levels of the company to act as hands-on coaches, not &#39;managers&#39;&lt;/li&gt;
&lt;li&gt;Designing the organization into small, high-performance teams that set their own targets&lt;/li&gt;
&lt;li&gt;Creating customer interactions within all groups and functions in the company&lt;/li&gt;
&lt;li&gt;Delivering a strong, focused mission and values to keep everyone aligned&lt;/li&gt;
&lt;li&gt;Creating systems with lots of transparent information, i.e., what are our goals, who is working on what project, who are our experts&lt;/li&gt;
&lt;li&gt;Implementing &#39;systems of engagement&#39; not just &#39;systems of record,&#39; i.e., collaboration, information-sharing, project management&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Building a focus on continuous learning and learning culture at all levels&lt;/b&gt;&lt;/li&gt;
&lt;li&gt;Implementing a strong external employment brand that attracts &#39;the right type&#39; of people&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Hiring and promoting experts, not general managers&lt;/b&gt;&lt;/li&gt;
&lt;li&gt;Encouraging and teaching people to give each other direct feedback&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Creating programs for peer-to-peer rewards and recognition&lt;/b&gt;&lt;/li&gt;
&lt;li&gt;Developing programs to foster diversity in teams&quot;&lt;/li&gt;
&lt;/ul&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;i&gt;What is Agile HR? And is it right for you?&lt;/i&gt;. (2016). HRSG. Retrieved on April 7, 2017 from&amp;nbsp;&lt;a href=&quot;http://resources.hrsg.ca/blog/what-is-agile-hr-and-is-it-right-for-you&quot;&gt;http://resources.hrsg.ca/blog/what-is-agile-hr-and-is-it-right-for-you&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;i&gt;Agile Model of HR&lt;/i&gt;. (n.d.). Bersin by Deloitte. Retrieved on April 7, 2017 from&amp;nbsp;&lt;a href=&quot;https://www.bersin.com/Lexicon/details.aspx?id=15373&quot;&gt;https://www.bersin.com/Lexicon/details.aspx?id=15373&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Bersin, Josh. (2012). &lt;i&gt;Building the Agile Enterprise: A New Model for HR&lt;/i&gt;. Bersin by Deloitte. Retrieved on April 7, 2017 from&amp;nbsp;&lt;a href=&quot;https://www.slideshare.net/jbersin/impact-2012-keynote-josh-bersin&quot;&gt;https://www.slideshare.net/jbersin/impact-2012-keynote-josh-bersin&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/266671905292959275/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/04/agile-model-of-hr.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/266671905292959275'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/266671905292959275'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/04/agile-model-of-hr.html' title='Agile Model of HR'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-340242853283546203</id><published>2017-04-07T00:01:00.004-07:00</published><updated>2017-04-07T00:03:04.479-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Jack Welch on the Role of HR</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;div style=&quot;text-align: left;&quot;&gt;
&quot;HR is the driving force behind what makes a winning team. We make the argument that the team that fields the best players wins. HR&#39;s involved in making sure we field the best players.&quot;&lt;/div&gt;
&lt;div style=&quot;text-align: left;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;iframe allowfullscreen=&quot;&quot; class=&quot;YOUTUBE-iframe-video&quot; data-thumbnail-src=&quot;https://i.ytimg.com/vi/rByDmC0SqtM/0.jpg&quot; frameborder=&quot;0&quot; height=&quot;266&quot; src=&quot;https://www.youtube.com/embed/rByDmC0SqtM?feature=player_embedded&quot; width=&quot;320&quot;&gt;&lt;/iframe&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/340242853283546203/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/04/jack-welch-on-role-of-hr.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/340242853283546203'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/340242853283546203'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/04/jack-welch-on-role-of-hr.html' title='Jack Welch on the Role of HR'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://img.youtube.com/vi/rByDmC0SqtM/default.jpg" height="72" width="72"/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-7026448065796117740</id><published>2017-04-03T03:34:00.001-07:00</published><updated>2017-04-03T03:35:08.329-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Agile Methodologies"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Unleashing Productivity</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;b&gt;Eliminate Bureaucratic Drag&lt;/b&gt;&lt;br /&gt;
&quot;More people are working in big, bureaucratic organizations than ever before. Yet there’s compelling evidence that bureaucracy creates a significant drag on productivity and organizational resilience and innovation.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;The average company loses more than 25% of its productive power to organizational drag, processes that waste time and prevent people from getting things done.... This often happens as a company grows, as the tendency is to put processes in place to replace judgement.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;A myriad of studies have documented the time lost to low-value management processes, from budgeting to the performance review....[A]s much as 50% of all internal compliance activity is of questionable value.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Create Pockets of Excellence&lt;/b&gt;&lt;br /&gt;
&quot;The average company follows a method of unintentional egalitarianism, spreading star talent across all of the roles.... Companies like Google and Apple, however, follow an intentionally non-egalitarian method. &#39;They select a handful of roles that are business critical, affecting the success of the company’s strategy and execution, and they fill 95% of these roles with A-level quality&#39;....&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;In addition, rewards were applied to team performance; no one person on the team could receive an exceptional performance appraisal unless the entire team did.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&#39;For every member of the team that is not a star player, productivity declines&#39;.... &#39;If 100% of the team is star players, productivity is extremely high.&#39;&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Raise Workforce Engagement&lt;/b&gt;&lt;br /&gt;
&quot;An engaged employee is 44% more productive than a satisfied worker, but an employee who feels inspired at work is nearly 125% more productive than a satisfied one.... The companies that inspire more employees perform better than the rest.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Vozza, Stephanie. (2017). &lt;i&gt;Why Employees At Apple and Google Are More Productive. &lt;/i&gt;Fast Company. Retrieved on April 3, 2017 from&amp;nbsp;&lt;a href=&quot;https://www.fastcompany.com/3068771/how-employees-at-apple-and-google-are-more-productive&quot;&gt;https://www.fastcompany.com/3068771/how-employees-at-apple-and-google-are-more-productive&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Hamel, Gary and Zanini, Michele. (2016). &lt;i&gt;Excess Management Is Costing U.S. $3 Trillion Per Year&lt;/i&gt;. Harvard Business Review. Retrieved on April 3, 2017 from&amp;nbsp;&lt;a href=&quot;https://hbr.org/2016/09/excess-management-is-costing-the-us-3-trillion-per-year&quot;&gt;https://hbr.org/2016/09/excess-management-is-costing-the-us-3-trillion-per-year&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/7026448065796117740/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/04/unleashing-productivity.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/7026448065796117740'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/7026448065796117740'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/04/unleashing-productivity.html' title='Unleashing Productivity'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-4059606944031094636</id><published>2017-03-30T07:24:00.000-07:00</published><updated>2017-04-03T03:42:10.186-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Innovation"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>The Future of Work</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;b&gt;On Hierarchy&lt;/b&gt;&lt;br /&gt;
&quot;In the old way of thinking, organizations were shaped like pyramids with all of the power and communication flowing from the top to the bottom. That meant that executives controlled everything about the company and the smaller workers at the bottom were simply powerless cogs in the machine. The system may have worked well in the olden days of agriculture and manufacturing, but it is completely outdated today.&lt;b&gt; Hierarchy breeds bureaucracy and red tape and makes it difficult for anyone to have a voice.&lt;/b&gt; &lt;b&gt;Instead, organizations are looking to flatten out and to give power to employees at all levels.&lt;/b&gt;&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;On Work Hours&lt;/b&gt;&lt;br /&gt;
&quot;A continuing concern for employees in 2016 is the increased need for flexibility. [...] With the availability of technology, remote offices and telecommunications, there is no reason why employees cannot be offered flexibility by employers.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;b&gt;Employees are much more productive when they can choose a work schedule and location that fits their lifestyle, whether that&#39;s working early mornings from home or evenings from a shared work space.&lt;/b&gt; The workplace is increasingly global, which means employers needs to be flexible to make sure they employees can work and connect with whoever they need to.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;On Annual Performance Reviews&lt;/b&gt;&lt;br /&gt;
&quot;HR managers don&#39;t find the reviews effective, and they can often be incredibly stressful to employees. After all, can a single once-yearly meeting really dictate your workplace success and pay? Instead, forward-thinking organizations are moving to more frequent conversations that are less formal. These &lt;b&gt;real-time check-ins allow employees and managers to touch base to discuss projects and get feedback in a way that is more accessible and useful to implementing change right away.&lt;/b&gt;&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Morgan, Jacob. (2017). &lt;i&gt;5 Workplace Practices That Are on Their Way Out&lt;/i&gt;. Inc.. Retrieved on March 30, 2017 from&amp;nbsp;&lt;a href=&quot;https://www.inc.com/jacob-morgan/5-work-practices-that-are-on-their-way-out.html&quot;&gt;https://www.inc.com/jacob-morgan/5-work-practices-that-are-on-their-way-out.html&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Young Entrepreneur Council. (2015). &lt;i&gt;10 Workplace Trends That Will Change the Way You Manage&lt;/i&gt;. Inc.. Retrieved on March 30, 2017 from&amp;nbsp;&lt;span style=&quot;text-align: left;&quot;&gt;&lt;a href=&quot;https://www.inc.com/young-entrepreneur-council/10-workplace-trends-that-will-change-the-way-you-manage.html&quot;&gt;https://www.inc.com/young-entrepreneur-council/10-workplace-trends-that-will-change-the-way-you-manage.html&lt;/a&gt;&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/4059606944031094636/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/03/the-future-of-work.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/4059606944031094636'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/4059606944031094636'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/03/the-future-of-work.html' title='The Future of Work'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-6731390227681724737</id><published>2017-03-28T00:48:00.000-07:00</published><updated>2017-03-28T01:03:25.293-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Entrepreneurship"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Lessons from the Gig Economy</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;The most impactful lesson that traditional companies can learn from the gig economy is to judge all workers, including employees, on their results, not on when and where they do their work.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;Not one study suggests that working in an office eight hours a day, five days a week maximizes employee productivity, satisfaction, or performance. In fact, any data that exists on work in an office reveals that most employees &lt;a href=&quot;http://www.gallup.com/poll/188144/employee-engagement-stagnant-2015.aspx&quot; target=&quot;_blank&quot;&gt;aren’t engaged&lt;/a&gt;, waste a lot of time in the office &lt;a href=&quot;http://www.forbes.com/sites/cherylsnappconner/2015/07/31/wasting-time-at-work-the-epidemic-continues/#67a55ff53ac1&quot; target=&quot;_blank&quot;&gt;not working&lt;/a&gt;, and that employee underperformance persists despite the omnipresence of management. Even worse, the direct costs of maintaining the traditional office-based workplace are high. CBRE estimates that the typical company in the U.S. spends upward of $12,000 per employee per year for office space. It’s hard to find a return-on-investment case for office space, and much harder still to find any company that makes a compelling one.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;a href=&quot;http://www.sciencealert.com/working-remotely-makes-you-happier-and-more-productive&quot; target=&quot;_blank&quot;&gt;Study&lt;/a&gt; after &lt;a href=&quot;http://www.forbes.com/sites/victorlipman/2016/05/02/are-remote-workers-happier-and-more-productive-new-survey-offers-answers/#150a6f14455c&quot; target=&quot;_blank&quot;&gt;study&lt;/a&gt; after &lt;a href=&quot;http://www.apa.org/pubs/journals/releases/apl-9261524.pdf&quot; target=&quot;_blank&quot;&gt;study&lt;/a&gt; demonstrate that independent, remote workers are more productive, satisfied, and engaged than their office-bound colleagues. Recent surveys of 8,000 workers by &lt;a href=&quot;http://www.mckinsey.com/global-themes/employment-and-growth/independent-work-choice-necessity-and-the-gig-economy&quot; target=&quot;_blank&quot;&gt;McKinsey’s Global Institute&lt;/a&gt; and nearly 900 independent workers by &lt;a href=&quot;http://info.fieldnation.com/rise-of-the-blended-workforce-in-gig-economy&quot; target=&quot;_blank&quot;&gt;Future Workplace and Field Nation&lt;/a&gt; find that those workers, freed from the constraints of office life, report higher levels of satisfaction and greater productivity. These results aren’t surprising since remote work eliminates the wasted time of commuting, the stress of constant exposure to office politics, and the death of the workday by a thousand paper cuts of interruptions and meetings.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;b&gt;[M]ost managers enjoy working at a company in which employees are managed by time and place. After all, it’s pretty easy to see who is at their desk between 9 and 5. It’s much harder to develop, measure, and evaluate the specific value and results that each employee produces. Managers will have to work a lot harder under a system that focuses on tracking performance, instead of time in an office chair.&lt;/b&gt;&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;b&gt;Labor is the most expensive and valuable resource at most firms. Managing this resource by time and place is a crude, empirically unproven, inefficient, and costly approach. The biggest lessons that companies can learn from the gig economy are to separate work from the office, and to measure employees based on what they produce, deliver and solve, not the hours they spend in the office. Put simply, companies need to stop measuring what doesn’t matter, and start measuring what does.&lt;/b&gt;&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Mulcahy, Diane. (2017). &lt;i&gt;Will the Gig Economy Make the Office Obsolete?&lt;/i&gt;. &amp;nbsp;Harvard Business Review. Retrieved on March 28, 2017 from&amp;nbsp;&lt;a href=&quot;https://hbr.org/2017/03/will-the-gig-economy-make-the-office-obsolete&quot;&gt;https://hbr.org/2017/03/will-the-gig-economy-make-the-office-obsolete&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/6731390227681724737/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/03/lessons-from-gig-economy.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/6731390227681724737'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/6731390227681724737'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/03/lessons-from-gig-economy.html' title='Lessons from the Gig Economy'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-1169088320523635617</id><published>2017-03-24T00:38:00.002-07:00</published><updated>2017-03-24T00:39:18.860-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Entrepreneurship"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Steve Jobs On Leadership, Management and Hiring</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: left;&quot;&gt;
&quot;The greatest people are self-managing. They don&#39;t need to be managed. Once they know that to do, they will go, figure out how to do it. They don&#39;t need to be managed at all. What they need is a common vision. That is what leadership is. Leadership is having a vision, being able to articulate that so the people around you can understand it and getting consensus on the common vision.&quot;&lt;/div&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;iframe width=&quot;320&quot; height=&quot;266&quot; class=&quot;YOUTUBE-iframe-video&quot; data-thumbnail-src=&quot;https://i.ytimg.com/vi/rQKis2Cfpeo/0.jpg&quot; src=&quot;https://www.youtube.com/embed/rQKis2Cfpeo?feature=player_embedded&quot; frameborder=&quot;0&quot; allowfullscreen&gt;&lt;/iframe&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/1169088320523635617/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/03/steve-jobs-on-leadership-management-and.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/1169088320523635617'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/1169088320523635617'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/03/steve-jobs-on-leadership-management-and.html' title='Steve Jobs On Leadership, Management and Hiring'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://img.youtube.com/vi/rQKis2Cfpeo/default.jpg" height="72" width="72"/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-9162984262081034749</id><published>2017-03-21T02:21:00.000-07:00</published><updated>2017-03-21T02:32:23.795-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Excellence"/><category scheme="http://www.blogger.com/atom/ns#" term="Human Dynamics"/><category scheme="http://www.blogger.com/atom/ns#" term="Learning"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Cognitive Assessments More Reliable Than Interviews At Predicting Employee Success</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;Tricia Prickett and Neha Gada-Jain, two psychology students at the University of Toledo, collaborated with their professor Frank Bernieri and reported in a 2000 study that judgments made in the first 10 seconds of an interview could predict the outcome of the interview.&lt;br /&gt;
&lt;br /&gt;
The problem is, these predictions from the first 10 seconds are useless.&lt;br /&gt;
&lt;br /&gt;
They create a situation where an interview is spent trying to confirm what we think of someone, rather than truly assessing them. Psychologists call this confirmation bias, “the tendency to search for, interpret, or prioritize information in a way that confirms one’s beliefs or hypotheses.” Based on the slightest interaction, we make a snap, unconscious judgment heavily influenced by our existing biases and beliefs. Without realizing it, we then shift from assessing a candidate to hunting for evidence that confirms our initial impression.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;&quot;In other words, most interviews are a waste of time because 99.4 percent of the time is spent trying to confirm whatever impression the interviewer formed in the first ten seconds.&quot;&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
&quot;In 1998, Frank Schmidt and John Hunter published a meta-analysis of 85 years of research on how well assessments predict performance. &lt;b&gt;They looked at 19 different assessment techniques and found that typical, unstructured job interviews were pretty bad at predicting how someone would perform once hired.&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Unstructured interviews have an r2 of 0.14, meaning that they can explain only 14 percent of an employee’s performance. This is somewhat ahead of reference checks (explaining 7 percent of performance), ahead of the number of years of work experience (3 percent).&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;b&gt;The best predictor of how someone will perform in a job is a work sample test (29 percent). &lt;/b&gt;This entails giving candidates a sample piece of work, similar to that which they would do in the job, and assessing their performance at it.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;b&gt;The second-best predictors of performance are tests of general cognitive ability (26 percent).&lt;/b&gt; In contrast to case interviews and brainteasers, these are actual tests with defined right and wrong answers, similar to what you might find on an IQ test. &lt;b&gt;They are predictive because general cognitive ability includes the capacity to learn, and the combination of raw intelligence and learning ability will make most people successful in most jobs.&lt;/b&gt;&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;Last year’s Wall Street Journal story on the legal implications of personality testing received substantial circulation. And it shed light on some of the limitations of personality testing:&lt;b&gt; an employee’s personality does not predict whether the person can learn the job tasks quickly or think critically.&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
With the average length of an employee’s job tenure at three (3) years for employees between the ages of 25-34, it’s increasingly important to identify job applicants who can be effective on the job, quickly.&lt;br /&gt;
&lt;br /&gt;
Hiring managers will turn to objective pre-employment tests that can evaluate whether a candidate can do the job or learn the job quickly, such as Cognitive Tests and Work Sample (Simulation) tests.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Personnel Testing Council presenter Dr. Scott Highhouse reminded a group of practitioners in November that cognitive assessments are even more reliable than structured interviews at predicting employee success.&lt;/b&gt;&quot;&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Bock, Lazlo. (2015). &lt;i&gt;Here&#39;s Google&#39;s Secret to Hiring the Best People&lt;/i&gt;. Wired Business, Retrieved on March 21, 2017 from&amp;nbsp;&lt;a href=&quot;https://www.wired.com/2015/04/hire-like-google/&quot;&gt;https://www.wired.com/2015/04/hire-like-google/&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Appelman, Shoa. (2015). &lt;i&gt;5 Pre-Employment Test Trends You Need To Know About&lt;/i&gt;. TLNT Talent Management and HR, Retrieved on March 21, 2017 from&amp;nbsp;&lt;a href=&quot;https://www.eremedia.com/tlnt/5-pre-employment-test-trends-you-need-to-know-about/&quot;&gt;https://www.eremedia.com/tlnt/5-pre-employment-test-trends-you-need-to-know-about/&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/9162984262081034749/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/03/cognitive-assessments-more-reliable.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/9162984262081034749'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/9162984262081034749'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/03/cognitive-assessments-more-reliable.html' title='Cognitive Assessments More Reliable Than Interviews At Predicting Employee Success'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-1179724271709698739</id><published>2017-03-17T02:11:00.001-07:00</published><updated>2017-03-17T02:11:32.907-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Agile Methodologies"/><category scheme="http://www.blogger.com/atom/ns#" term="Innovation"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Empowering Knowledge Workers</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;ROWE (&lt;a href=&quot;https://en.wikipedia.org/wiki/ROWE&quot; target=&quot;_blank&quot;&gt;results only work environment&lt;/a&gt;) is a fantastic framework that needs to be adopted in places employing knowledge workers. &lt;b&gt;You should be measuring the output of your workers, not the amount of time you can see them sitting in your office.&lt;/b&gt; [...] If you really think your employees will not be working if you cannot look over their shoulder to check, you have the wrong way of looking at the relationship with your employees... You should be hiring people who are engaged by their work and believe in the company’s mission. If people slack off when you aren’t watching them, your company has a disease, and you have discovered a symptom. You cannot treat this symptom and expect the disease to be cured.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;b&gt;In the case of working from home/remote work,&lt;/b&gt; some employees do not do their best work from home, or simply don’t like it. That is fine—but &lt;b&gt;you should trust your employees and treat them like adults. Let them make the call for themselves.&lt;/b&gt; Remove the training wheels and let them fail. If they cannot succeed in a hands off environment, do you really think babysitting them is going to work?&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;In &#39;&lt;a href=&quot;https://medium.com/@yanismydj/introduce-process-only-as-a-last-resort-21bd25e53eb#.5e3l1n75e&quot; target=&quot;_blank&quot;&gt;Introduce Process Only As A Last Resort&lt;/a&gt;,&#39; we look at how process often times helps the bad and hurts the good. Bad actors in an organization will figure out what the rules and the process are and follow them to a letter. Then they’ll find a way to slack off within these boundaries.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;b&gt;Before introducing new process, ask yourself and those in your organization, &lt;i&gt;what is the problem we’re trying to solve? Is there any way we can solve this problem without creating a new system?&lt;/i&gt; Even something as simple as a basic rule can subvert a team member’s intrinsic motivation.&lt;/b&gt; Think of it this way: if you hand fed someone everyday of their life, this individual would be reliant on you feeding them to survive. They would not have discovered that they need to find a food source 3+ times a day in order to survive. They might eventually figure it out, but it would be a challenging transition. It would require a much more conscious effort to stay satiated and able to focus on other goals.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;b&gt;Without process everywhere, it makes the lives of management harder. This is one of the reasons middle managers love process. However, the goal of an organization should not to be to provide cushy jobs for middle managers.&lt;/b&gt; This job should be hard, and it is not for everyone. It requires people skills, leadership, and an almost super human ability to stay in tune with a team. It is very hard to find good leaders who can do this job well. [...] &lt;b&gt;Bad middle managers can utilize the burdensome process to their advantage just as easily as bad actors on the front lines. Great leaders do not need rules or process. Those who follow them do so willingly, and do amazing things with their autonomy.&lt;/b&gt; They relay the right information back from the front lines, good or bad, and make key suggestions which often make or break the outcome of battles.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;Fight the introduction of process at all costs. Empower your employees and your fellow team members by avoiding it. Believe in the people around you, and if they fail, keep the safety net just harsh enough that a lesson will be learned. &lt;b&gt;Counter intuitively, less process will help your organization run smoother, and ensure it is filled with the right kind of people.&lt;/b&gt;&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Lhert, Yan. (2017). &lt;i&gt;If you don’t trust your employees to work remotely, you shouldn’t have hired them in the first place&lt;/i&gt;. Quartz. Retrieved on March 17, 2016 from &lt;a href=&quot;https://qz.com/891537/if-you-dont-trust-your-employees-to-work-remotely-you-shouldnt-have-hired-them-in-the-first-place/&quot; target=&quot;_blank&quot;&gt;https://qz.com/891537/if-you-dont-trust-your-employees-to-work-remotely-you-shouldnt-have-hired-them-in-the-first-place/&amp;nbsp;&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Lhert, Yan. (2016). &lt;i&gt;Introduce Process Only As A Last Resort&lt;/i&gt;. Medium. Retrieved on March 17, 2017 from&amp;nbsp;&lt;a href=&quot;https://medium.com/@yanismydj/introduce-process-only-as-a-last-resort-21bd25e53eb#.s9ze5kgv6&quot;&gt;https://medium.com/@yanismydj/introduce-process-only-as-a-last-resort-21bd25e53eb#.s9ze5kgv6&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/1179724271709698739/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/03/empowering-knowledge-workers.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/1179724271709698739'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/1179724271709698739'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/03/empowering-knowledge-workers.html' title='Empowering Knowledge Workers'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-3888626854298411186</id><published>2017-03-13T03:50:00.001-07:00</published><updated>2017-03-13T03:57:02.654-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Innovation"/><category scheme="http://www.blogger.com/atom/ns#" term="Learning"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>A Culture of Learning and Innovation</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;A &#39;learning culture&#39; is an organization-wide belief that the company’s strategy, mission, and operations can continuously be improved through an ongoing process of individual and organizational learning. It includes a set of investments, programs, and processes to study areas of weakness, explore causes, and exploit opportunities to improve and learn at all times and at all levels.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;A sustainable culture of innovation requires organisation-wide commitment. It must be driven from the top-down. Executives, managers and people leaders all have a role to play to endorse creativity, idea-sharing and collaboration. Although most organisations encouraged creativity and innovation as a corporate value, for many it wasn’t underpinned by other aspects required to create a thriving culture of innovation. Absent for many was a culture that promoted risk-taking and entrepreneurial behaviour, and an environment of trust in which employees could challenge existing assumptions, try new ideas, and fail.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;Recognizing and rewarding innovation is key to establishing a culture of innovation. There was a mismatch between the number of organisations that say they recognise and reward innovation, and those with established performance management practices for doing so. This suggests that companies are willing to adopt innovative processes without the support of HR. Innovation cannot be truly optimised without ongoing, iterative feedback. Despite a market shift in emphasis from annual performance reviews to continuous feedback, the majority of companies aren’t there yet.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Skilbeck, Rebecca. (2017). &lt;i&gt;Driving a Culture of Innovation&lt;/i&gt;. PageUp Talent Lab. Retrieved on March 13, 2017 from&amp;nbsp;&lt;a href=&quot;https://www.pageuptalentlab.com/driving-culture-innovation/&quot;&gt;https://www.pageuptalentlab.com/driving-culture-innovation/&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;i&gt;Learning Culture&lt;/i&gt;. (n.d.). Bersin by Deloitte. Retrieved on March 13, 2017 from&amp;nbsp;&lt;a href=&quot;http://www.bersin.com/lexicon/Details.aspx?id=13116&quot;&gt;http://www.bersin.com/lexicon/Details.aspx?id=13116&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/3888626854298411186/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/03/a-culture-of-learning-and-innovation.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/3888626854298411186'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/3888626854298411186'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/03/a-culture-of-learning-and-innovation.html' title='A Culture of Learning and Innovation'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-4768761314507542502</id><published>2017-03-08T02:56:00.001-08:00</published><updated>2017-03-08T02:56:22.417-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Human Dynamics"/><category scheme="http://www.blogger.com/atom/ns#" term="Innovation"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Time to Ditch Annual Performance Reviews?</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;When it comes to workplace events that produce resentment and anxiety, few score higher than the big annual performance review. Calls to end this time-consuming and often unproductive practice have gone unheeded — until now. Recently, Adobe, Kelly Services, GE, Deloitte and PwC have ended them, and the rippling out to smaller firms and other sectors appears to be underway. To which many say: good riddance.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;Other companies are rethinking their practices, too. Accenture’s 330,000 employees are undergoing what CEO Pierre Nanterme has called a “massive revolution” in which timely, personalized employee feedback is replacing annual evaluations and rankings. Whether you agree or disagree with UCLA researcher Samuel Culbert’s assessment that performance reviews are “a curse on corporate America,” it’s nonetheless clear that they’re falling out of favor.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;Companies such as Juniper and Adobe stopped giving people a one-to-five rating or evaluating employees on a “performance curve,” also known as the “forced ranking” approach. &lt;b&gt;They were still differentiating performance in various ways, and still using a pay-for-performance approach, just not through a simple rating system.&amp;nbsp;&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
By early 2015, around 30 large companies, representing over 1.5 million employees, were following a similar path. No longer defining performance by a single number, these companies were emphasizing ongoing, quality conversations between managers and their teams.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;To my way of thinking, a one-side-accountable, boss-administered review is little more than a dysfunctional pretense. It&#39;s a negative to corporate performance, an obstacle to straight-talk relationships, and a prime cause of low morale at work. Even the mere knowledge that such an event will take place damages daily communications and teamwork.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;b&gt;Once-a-year goals are too “batched” for a real-time world, and conversations about year-end ratings are generally less valuable than conversations conducted in the moment about actual performance.&amp;nbsp;&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
But the need for change didn’t crystallize until we decided to count things. Specifically, we tallied the number of hours the organization was spending on performance management—and found that completing the forms, holding the meetings, and creating the ratings consumed close to 2 million hours a year. As we studied how those hours were spent, we realized that many of them were eaten up by leaders’ discussions behind closed doors about the outcomes of the process. We wondered if we could somehow shift our investment of time from talking to ourselves about ratings to talking to our people about their performance and careers—from a focus on the past to a focus on the future.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Buckingham, Marcus and Goodall, Ashley. (2015). &lt;i&gt;Reinventing Performance Management. &lt;/i&gt;Harvard Business Review. Retrieved on March 8, 2017 from&amp;nbsp;&lt;span style=&quot;text-align: left;&quot;&gt;&lt;a href=&quot;https://hbr.org/2015/04/reinventing-performance-management&quot;&gt;https://hbr.org/2015/04/reinventing-performance-management&lt;/a&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Duggan, Kris. (2015). &lt;i&gt;Why The Annual Performance Review Is Going Extinct&lt;/i&gt;. The Future of Work. Retrieved on March 8. 2017 from &amp;nbsp;&lt;a href=&quot;https://www.fastcompany.com/3052135/the-future-of-work/why-the-annual-performance-review-is-going-extinct&quot;&gt;https://www.fastcompany.com/3052135/the-future-of-work/why-the-annual-performance-review-is-going-extinct&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Rock, David and Jones, Beth. (2015). &lt;i&gt;Why More and More Companies Are Ditching Performance Ratings&lt;/i&gt;. Harvard Business Review. Retrieved on March 8, 2017 from&amp;nbsp;&lt;a href=&quot;https://hbr.org/2015/09/why-more-and-more-companies-are-ditching-performance-ratings&quot;&gt;https://hbr.org/2015/09/why-more-and-more-companies-are-ditching-performance-ratings&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;i&gt;The End of Annual Performance Reviews: Are the Alternatives Any Better?&lt;/i&gt;. (2016). Knowledge@Wharton. Retrieved on March 8. 2017 from&amp;nbsp;&lt;a href=&quot;http://knowledge.wharton.upenn.edu/article/the-end-of-annual-performance-reviews/&quot;&gt;http://knowledge.wharton.upenn.edu/article/the-end-of-annual-performance-reviews/&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/4768761314507542502/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/03/time-to-ditch-annual-performance-reviews.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/4768761314507542502'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/4768761314507542502'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/03/time-to-ditch-annual-performance-reviews.html' title='Time to Ditch Annual Performance Reviews?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-6145189299412688385</id><published>2017-03-02T06:00:00.002-08:00</published><updated>2017-03-02T06:00:46.282-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Entrepreneurship"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Want to Raise Productivity? Let Employees Work From Home</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;The results we saw at Ctrip blew me away. Ctrip was thinking that it could save money on space and furniture if people worked from home and that the savings would outweigh the productivity hit it would take when employees left the discipline of the office environment. Instead, we found that people working from home completed 13.5% more calls than the staff in the office did—meaning that Ctrip got almost an extra workday a week out of them. They also quit at half the rate of people in the office—way beyond what we anticipated. And predictably, at-home workers reported much higher job satisfaction.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;One-third of the productivity increase, we think, was due to having a quieter environment, which makes it easier to process calls. At home people don’t experience what we call the “cake in the break room” effect. Offices are actually incredibly distracting places. The other two-thirds can be attributed to the fact that the people at home worked more hours. They started earlier, took shorter breaks, and worked until the end of the day. They had no commute. They didn’t run errands at lunch. Sick days for employees working from home plummeted. Search “working remotely” on the web, and everything that comes up will be supernegative and say that telecommuters don’t work as hard as people in the office. But actually, it’s quite the opposite.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Bloom, Nicholas. (2014).&amp;nbsp;&lt;i&gt;To Raise Productivity, Let More Employees Work from Home&lt;/i&gt;. Harvard Business Review. Retrieved on March 2, 2017 from&amp;nbsp;&lt;a href=&quot;https://hbr.org/2014/01/to-raise-productivity-let-more-employees-work-from-home&quot;&gt;https://hbr.org/2014/01/to-raise-productivity-let-more-employees-work-from-home&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/6145189299412688385/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/03/want-to-raise-productivity-let.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/6145189299412688385'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/6145189299412688385'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/03/want-to-raise-productivity-let.html' title='Want to Raise Productivity? Let Employees Work From Home'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-6423712780592416587</id><published>2017-02-27T01:00:00.000-08:00</published><updated>2017-02-27T01:01:52.460-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Entrepreneurship"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Making Remote Work Work</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;&lt;b&gt;Hire the right people.&lt;/b&gt; Having remote team members requires that we hire people who can deliver technically while working independently. At the same time, the fact that we do not have to maintain physical offices leaves us room to pay higher wages than others and attract top talent.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;b&gt;Focus on outcomes.&lt;/b&gt; After spending as much effort as we do in bringing the right people into the firm, it only makes sense to set them free. The first and most important step in doing this is to set expectations. We tell our new teammates exactly what outcomes matter to us, and reward them for achieving and exceeding those outcomes.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;b&gt;Help employees choose, and be responsible for, their own adventure.&lt;/b&gt; By determining the right floor and not restricting the ceiling, and by paying for value (once they exceed their outcome, consultants are paid a commission proportional to the additional work they deliver), we put the choice of how hard to work in a consultant’s hands.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;Outside of client work, we allow teammates to invest in other areas, and even provide them resources when required. For instance, we often announce an innovation budget and invite applications to pilot ideas. As a result, our teammates voluntarily design new practice areas, conduct cutting-edge leadership research, and write books. We’ve noticed that our team members adopt a strong sense of commitment to the responsibilities they take on and do not abandon them when the going gets tough. They feel true ownership. &lt;b&gt;Our leadership team ensures that this balance between choice and commitment, and the value of owning the outcome, is a respected, celebrated cultural attribute.&lt;/b&gt;&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;&lt;b&gt;Centralize thoughtfully.&lt;/b&gt; We focus on letting our team members be the “CEOs” of their professional lives, but we have learned over time that not every aspect of choice adds value. For example, we previously enabled consultants to choose their own health care plan providers, and even set up their home office the way they wanted, but have since moved to a company plan and standard IT package to launch our team. This makes their lives easier without taking away the choices that truly matter. While there are more instances of such centralization, &lt;b&gt;our leadership team maintains a very high bar for such decisions because too much control can erode mutual trust.&lt;/b&gt;&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Street, Randy, Wang, Dina, and Tetali, Vamsi. (2017). &lt;i&gt;What 20 years as a Remote Organization Has Taught Us About Managing Remote Teams&lt;/i&gt;. Harvard Business Review. Retrieved on February 27, 2017 from&amp;nbsp;&lt;a href=&quot;https://hbr.org/2017/02/what-20-years-as-a-remote-organization-has-taught-us-about-managing-remote-teams&quot;&gt;https://hbr.org/2017/02/what-20-years-as-a-remote-organization-has-taught-us-about-managing-remote-teams&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/6423712780592416587/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/02/making-remote-work-work.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/6423712780592416587'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/6423712780592416587'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/02/making-remote-work-work.html' title='Making Remote Work Work'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-5793521111627697509</id><published>2017-02-19T03:18:00.001-08:00</published><updated>2017-02-19T03:27:56.983-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Excellence"/><category scheme="http://www.blogger.com/atom/ns#" term="Learning"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>Learning to Learn</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;b&gt;&quot;The ability to learn faster than your competitors may be the only sustainable competitive advantage.&quot;&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
&quot;Learning organizations are skilled at five main activities: systematic problem solving, experimentation with new approaches, learning from their own experience and past history, learning from the experiences and best practices of others, and transferring knowledge quickly and efficiently throughout the organization.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;Learning organizations are not built overnight. Most successful examples are the products of carefully cultivated attitudes, commitments, and management processes that have accrued slowly and steadily over time. Still, some changes can be made immediately. Any company that wishes to become a learning organization can begin by taking a few simple steps.&lt;br /&gt;
&lt;br /&gt;
The first step is to foster an environment that is conducive to learning. There must be time for reflection and analysis, to think about strategic plans, dissect customer needs, assess current work systems, and invent new products. Learning is difficult when employees are harried or rushed; it tends to be driven out by the pressures of the moment. Only if top management explicitly frees up employees’ time for the purpose does learning occur with any frequency. That time will be doubly productive if employees possess the skills to use it wisely. Training in brainstorming, problem solving, evaluating experiments, and other core learning skills is therefore essential.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
de Geus, Arie P. (1988). &lt;i&gt;Planning as Learning.&lt;/i&gt;&amp;nbsp;Harvard Business Review. Retrieved on February 19, 2017 from&amp;nbsp;&lt;a href=&quot;https://hbr.org/1988/03/planning-as-learning&quot;&gt;https://hbr.org/1988/03/planning-as-learning&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Garvin, David A. (1993). &lt;i&gt;Building a Learning Organization. &lt;/i&gt;Harvard Business Review. Retrieved on February 19, 2017 from&amp;nbsp;&lt;a href=&quot;https://hbr.org/1993/07/building-a-learning-organization&quot;&gt;https://hbr.org/1993/07/building-a-learning-organization&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/5793521111627697509/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/02/the-learning-organization.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/5793521111627697509'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/5793521111627697509'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/02/the-learning-organization.html' title='Learning to Learn'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-8705246015834553202</id><published>2017-02-01T04:30:00.000-08:00</published><updated>2017-02-01T04:30:26.918-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Entrepreneurship"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><category scheme="http://www.blogger.com/atom/ns#" term="Technology Management"/><title type='text'>Knowledge-based View (KBV) of the Firm</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
The essential elements of the KBV can be summarized as follows:&lt;br /&gt;
&lt;br /&gt;
&lt;ul style=&quot;text-align: left;&quot;&gt;
&lt;li&gt;Knowledge is the most important resource and factor of production.&lt;/li&gt;
&lt;li&gt;Performance differences between firms exist because of differences in firms’ stock of knowledge and capabilities in using and developing knowledge.&lt;/li&gt;
&lt;li&gt;Organizations exist to create, transfer, and transform knowledge into competitive advantage.&lt;/li&gt;
&lt;li&gt;Knowledge is related to humans.&lt;/li&gt;
&lt;li&gt;Individuals are intentional and intelligent agents.&lt;/li&gt;
&lt;li&gt;Humans are bounded by cognitive limitations; how much and what they can know have cognitive limits, and therefore they have to specialize.&lt;/li&gt;
&lt;li&gt;Especially in complex issues which cannot be understood by any single individual, there is a need for integration and coordination of knowledge.&lt;/li&gt;
&lt;li&gt;Cognition and action are related: knowledge is both acquired by and demonstrated in action.&lt;/li&gt;
&lt;li&gt;Knowledge is demonstrated in many forms and located on many levels: it is situated in the minds and bodies of individuals, embedded in organizational routines and processes, as well as codified in databases and books etc.&lt;/li&gt;
&lt;li&gt;Some knowledge can be externalized into explicit form, while some knowledge will always remain tacit.&lt;/li&gt;
&lt;li&gt;The form of knowledge influences how it can be leveraged and transferred.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Shared tacit knowledge, demonstrated for example in capabilities, is the most important type of knowledge from the value creation point of view.&lt;/li&gt;
&lt;li&gt;Knowledge cannot be fully managed in the same sense as other types of resources; its management more resembles the creation of suitable contexts and cultivation.&lt;/li&gt;
&lt;li&gt;Knowledge is dynamic: it is continuously re-interpreted and modified, and related to learning and change.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Blomqvist, Kirsimarja and Kianto, Aino. (2015). &amp;nbsp;&lt;i&gt;Knowledge-based View of the Firm - Theoretical&amp;nbsp;Notions and Implications for Management&lt;/i&gt;. Retrieved on February 1, 2017 from&amp;nbsp;&lt;a href=&quot;http://www.lut.fi/documents/10633/109602/tijo-valintakoeartikkeli-2015.pdf&quot;&gt;http://www.lut.fi/documents/10633/109602/tijo-valintakoeartikkeli-2015.pdf&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/8705246015834553202/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/02/knowledge-based-view-kbv-of-firm.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/8705246015834553202'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/8705246015834553202'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/02/knowledge-based-view-kbv-of-firm.html' title='Knowledge-based View (KBV) of the Firm'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-6929576637115536503</id><published>2017-01-19T03:49:00.001-08:00</published><updated>2017-01-19T03:56:23.566-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Excellence"/><category scheme="http://www.blogger.com/atom/ns#" term="Human Dynamics"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><title type='text'>The Myth of the Bell Curve: Look for Hyper The Hyper-Performers</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;Think about how people perform in creative, service, and intellectual property businesses (where all businesses are going). There are superstars in every group. &lt;b&gt;Some software engineers are 10X more productive than the average&lt;/b&gt;; some sales people deliver 2-3X their peers; certain athletes far outperform their peers; musicians, artists, and even leaders are the same.&lt;br /&gt;
&lt;br /&gt;
These &lt;b&gt;&quot;hyper performers&quot; are people you want to attract, retain, and empower&lt;/b&gt;. These are the people who start companies, develop new products, create amazing advertising copy, write award winning books and articles, or set an example for your sales force. They are often gifted in a certain way (often a combination of skill, passion, drive, and energy) and they actually do drive orders of magnitude more value than many of their peers.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;If we&#39;re lucky we can attract a lot of these people - and when we do we should pay them very well, give them freedom to perform and help others, and take advantage of the work they do.&lt;/b&gt; Investment banks understand this - that&#39;s why certain people earn 10-fold more than others.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;People often believe the bell curve is &quot;fair.&quot; There are an equal number of people above and below the average. And fairness is very important. But fairness does not mean &quot;equality&quot; or &quot;equivalent rewards for all.&quot; &lt;b&gt;High performing companies have very wide variations in compensation, reflecting the fact that some people really do drive far more value than others.&lt;/b&gt; In a true meritocracy this is a good thing, as long as everyone has an opportunity to improve, information is transparent, and management is open and provides feedback.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Bersin, Josh. (2014).&amp;nbsp;&lt;i&gt;The Myth of the Bell Curve: Look for Hyper The Hyper-Performers. &lt;/i&gt;Retrieved on January 19, 2017 from&amp;nbsp;&lt;a href=&quot;http://www.forbes.com/sites/joshbersin/2014/02/19/the-myth-of-the-bell-curve-look-for-the-hyper-performers/#2e6acad613fc&quot;&gt;http://www.forbes.com/sites/joshbersin/2014/02/19/the-myth-of-the-bell-curve-look-for-the-hyper-performers/#2e6acad613fc&lt;/a&gt;&amp;nbsp;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/6929576637115536503/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/01/the-myth-of-bell-curve-look-for-hyper.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/6929576637115536503'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/6929576637115536503'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/01/the-myth-of-bell-curve-look-for-hyper.html' title='The Myth of the Bell Curve: Look for Hyper The Hyper-Performers'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1593068256845109312.post-3015648328453740062</id><published>2017-01-09T06:10:00.001-08:00</published><updated>2017-01-09T06:10:55.318-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Innovation"/><category scheme="http://www.blogger.com/atom/ns#" term="Organizational Theory"/><category scheme="http://www.blogger.com/atom/ns#" term="Technology Management"/><title type='text'>The Case for Expert Leaders</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&quot;[O]rganizations perform more effectively when led by individuals who have a deep understanding of the core business of their organization. Being a capable general manager is not sufficient. Expert leaders are those with (1) inherent knowledge, acquired through technical expertise combined with high ability in the core business activity; (2) industry experience, which stems from time and practice within the core business industry; and (3) leadership capabilities, which include management skills and a leader’s innate characteristics.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;[T]o lead creative individuals
requires both ‘technical and creative problem-solving skills’ since . . . ‘they provide a basis for structuring an inherently ill-defined task and because they provide
the credibility needed to exercise influence’.&quot;&lt;br /&gt;
&lt;br /&gt;
&quot;[F]irst, that the
evaluation of creative people and their ideas can only be done by individuals who share their
competencies; in short, it takes one to know one (or competently assess one). Second, leaders
who share the same creative and technical perspective and motivation as their followers can
communicate more clearly; finally, in relation to performance, they can better articulate the
needs and goals of the organization.&quot;&lt;br /&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Godall, Amanda H. (2012). &lt;i&gt;A Theory of Expert Leadership.&lt;/i&gt;&amp;nbsp;Retrieved on January 9, 2017 from&amp;nbsp;&lt;a href=&quot;http://ftp.iza.org/dp6566.pdf&quot;&gt;http://ftp.iza.org/dp6566.pdf&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://fluxir.blogspot.com/feeds/3015648328453740062/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://fluxir.blogspot.com/2017/01/the-case-for-expert-leaders.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/3015648328453740062'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1593068256845109312/posts/default/3015648328453740062'/><link rel='alternate' type='text/html' href='http://fluxir.blogspot.com/2017/01/the-case-for-expert-leaders.html' title='The Case for Expert Leaders'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>