Second-order competence is the ability to formulate, evaluate, implement, and follow up on an order so that the intended business goal is achieved. The term is often used in procurement, purchasing, project management, IT development, construction, consulting services, and the public sector, but is relevant in all situations where one party hires another to deliver a product, service, or change. It is easy to believe that second-order competence primarily involves writing requirements specifications or negotiating contracts. In practice, these are only visible expressions of something much deeper: the ability to understand what needs to be achieved, which quality requirements actually matter, and which uncertainties lie behind the supplier\u2019s offer. Second-order competence is therefore not just a process or a role. It should rather be considered a personal and organizational ability, what within strategic management is often called a capability<\/em>. An organization can have advanced purchasing processes and extensive governance documents but still lack real second-order competence if it does not understand the area where the ordering takes place.<\/p>\n\n\n\n The core of the client\u2019s expertise is domain knowledge. By domain knowledge, we mean a deep understanding of the area where the delivery is to take place, including:<\/p>\n\n\n\n Tacit knowledge is the experience-based knowledge that is often difficult to document but is crucial for success. Those who have performed the work themselves often know which elements are trivial and which are in practice very complex. The lack of such understanding can create a form of Dunning-Kruger effect, where the client overestimates their ability to understand and assess what is to be ordered. The result is often that the supplier\u2019s description of the problem is accepted uncritically, which in practice means that the supplier defines both the need and the solution. Therefore, client competence is not only about describing what is to be delivered. It is about understanding the difference between a delivery that technically meets a requirement and a delivery that actually creates the value requested. This article addresses second-order competence as a field of knowledge and highlights its historical development, practical application, relationship to other disciplines, and the risks that arise when second-order competence is lacking.<\/p>\n\n\n\n Historically, client competence has been closely linked to craft professions and construction projects. The client and contractor often had similar knowledge of the work to be performed. The difference lay primarily in resources and responsibilities. During industrialization, specialization increased. The client became, in many contexts, organizationally and knowledge-wise separated from the contractors. This created an information gap between the buyer and the supplier. In the 20th century, professional purchasing functions, procurement methods, and contract forms evolved. The focus was long on price, contracts, and delivery control. In recent decades, knowledge-intensive areas such as IT, cybersecurity, advanced technology, and management consulting have shown that contracts and processes are not enough. A client must understand enough about the field to be able to assess alternatives, risks, and quality. This has therefore evolved into a view where client competence is considered a strategic organizational resource.<\/p>\n\n\n\n Authoritative expertise exists in many areas:<\/p>\n\n\n\n The most central principle is that one must understand the area the order concerns. This does not mean that the ordering party has to be the foremost expert, but that they must understand:<\/p>\n\n\n\n People who have previously performed the work themselves often possess an important advantage because they are aware of the tacit knowledge that rarely appears in tenders and contracts.<\/p>\n\n\n\n A common mistake is to define activities instead of results. For example:<\/p>\n\n\n\n \u201dThe wall needs to be painted over.\u201d<\/p>\n\n\n\n This describes an activity but not the quality of the final result. A technically correct delivery can be:<\/p>\n\n\n\n A high-quality delivery, however, may require:<\/strong><\/p>\n\n\n\n The latter solution may cost ten times more than the first.<\/p>\n\n\n\n From a contract perspective, both interpretations can fulfill the phrase \u201dthe wall needs to be repainted.\u201d The client\u2019s task is therefore to define the desired result rather than simply the activity.<\/p>\n\n\n\n An important insight is that the supplier normally optimizes its operations based on its own goals. That does not mean that the supplier is dishonest, but it does have:<\/p>\n\n\n\n The client must therefore be able to make independent assessments.<\/p>\n\n\n\n Procurement expertise largely involves managing information asymmetry. Information asymmetry arises when one party knows significantly more than the other. The greater the knowledge gap between the buyer and the supplier, the greater the risk of:<\/p>\n\n\n\n The client\u2019s competence is influenced by several related areas; here are a few examples:<\/p>\n\n\n\n Example 1: Repainting of a wall<\/strong><\/p>\n\n\n\n The order: \u201dThe wall needs to be painted over.\u201d<\/p>\n\n\n\n Option A:<\/p>\n\n\n\n Results:<\/p>\n\n\n\n Option B:<\/p>\n\n\n\n Results:<\/p>\n\n\n\n The cost difference can be several hundred percent, even though both deliveries can formally be considered repainting.<\/p>\n\n\n\n Example 2: IT systems<\/strong><\/p>\n\n\n\n The order: \u201dWe need a new case management system.\u201d An inexperienced orderer focuses on functionality. An experienced orderer also analyzes:<\/p>\n\n\n\n The result is often a more expensive implementation but a lower total cost over the life of the system.<\/p>\n\n\n\n Client competence is essentially the ability to understand what should be achieved, how quality is defined, and the consequences of different solutions. It is based on a combination of experience, domain knowledge, judgment, and organizational learning. Those lacking client competence risk buying what is easy to describe rather than what is actually needed. This often leads to increased costs, conflicts, and lower quality.<\/p>\n\n\n\n Advantages<\/strong><\/p>\n\n\n\n Disadvantages, risks and limitations<\/strong><\/p>\n\n\n\n Five readiness questions<\/strong><\/p>\n\n\n\n Organizations should view procurement expertise as a strategic core capability rather than an administrative function. It arises through experience, domain knowledge, and systematic learning. The more knowledge-intensive the delivery is, the more important it becomes for the buyer to understand both the problem and the quality criteria before a solution is procured.<\/p>\n\n\n\n A useful rule of thumb is: The less one could perform the work themselves, the greater the need to invest in contracting expertise before ordering it.<\/strong><\/p>\n\n\n\n <\/p>","protected":false},"excerpt":{"rendered":" Best\u00e4llarkompetens: F\u00f6rm\u00e5gan att best\u00e4lla r\u00e4tt sak p\u00e5 r\u00e4tt s\u00e4tt Brief Best\u00e4llarkompetens \u00e4r f\u00f6rm\u00e5gan att formulera, v\u00e4rdera, genomf\u00f6ra och f\u00f6lja upp en best\u00e4llning s\u00e5 att det avsedda verksamhetsm\u00e5let uppn\u00e5s. Begreppet anv\u00e4nds ofta inom upphandling, ink\u00f6p, projektledning, IT-utveckling, byggnation, konsulttj\u00e4nster och offentlig sektor, men \u00e4r relevant i alla situationer d\u00e4r en part anlitar en annan f\u00f6r att […]<\/p>\n","protected":false},"author":2,"featured_media":0,"parent":0,"template":"","glossary-cat":[60],"class_list":["post-2259","glossary","type-glossary","status-publish","hentry","glossary-cat-definitioner"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n
\n\n\n\nHistory<\/h3>\n\n\n\n
\n\n\n\nApplication<\/h3>\n\n\n\n
\n
\n
Laws and regulations often require competitive bidding while complex business needs must be defined in an objective manner. The higher the complexity, the more important the contracting authority\u2019s competence becomes.<\/li>\n<\/ul>\n\n\n\n
\n\n\n\nWhat is central and important?<\/h3>\n\n\n\n
Domain knowledge is the basic prerequisite<\/h4>\n\n\n\n
\n
\n\n\n\nQuality must be defined<\/h4>\n\n\n\n
\n
\n
\n\n\n\nThe provider is not neutral<\/h4>\n\n\n\n
\n
\n\n\n\nUnderstanding information asymmetry<\/h4>\n\n\n\n
\n
\n\n\n\nEcosystem<\/h3>\n\n\n\n
\n
\n\n\n\nPractical examples<\/h4>\n\n\n\n
\n
\n
\n
\n
\n
\n\n\n\nSummary<\/h3>\n\n\n\n
\n
\n
\n
Recommendation<\/h4>\n\n\n\n