{"id":97896,"date":"2025-02-25T09:51:03","date_gmt":"2025-02-25T08:51:03","guid":{"rendered":"https:\/\/diselva.com\/2025\/02\/25\/nearshoring-series-part-4-technological-onboarding-how-it-works\/"},"modified":"2025-09-22T17:13:31","modified_gmt":"2025-09-22T15:13:31","slug":"nearshoring-series-part-4-technological-onboarding-how-it-works","status":"publish","type":"post","link":"https:\/\/diselva.com\/en\/blog\/nearshoring-series-part-4-technological-onboarding-how-it-works\/","title":{"rendered":"Nearshoring Series Part 4: How to Achieve Technological Onboarding"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">In the blog post about <strong>the collaboration success factors<\/strong> , I have already touched on the topic of onboarding. Again, the wrong approach can make or break and as already emphasized in the <strong>diselva Nearshore Excellence Framework<\/strong> , the success of a nearshore project depends not only on the technology, but also on a good integration of the teams. <\/p>\n\n\n\n<!--more-->\n\n\n\n<p class=\"wp-block-paragraph\">What should be <strong>avoided<\/strong> at all costs is simultaneous <strong>onboarding of the entire nearshoring team<\/strong>. This only leads to the fact that the people are not picked up, both personally and professionally. <strong>Frustration<\/strong> and loss of <strong>quality<\/strong> are inevitable. Step-by-step onboarding can ensure that knowledge can be shared within the nearshoring team and that there is enough time to answer open questions.    <\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" width=\"990\" height=\"800\" src=\"https:\/\/i0.wp.com\/diselva.com\/wp-content\/uploads\/2025\/07\/blogbild-EN-technologisches-onboarding-so-gelingts.png?resize=990%2C800&#038;quality=78&#038;ssl=1\" alt=\"Tech Onboarding - Roles\" class=\"wp-image-5108\" srcset=\"https:\/\/i0.wp.com\/diselva.com\/wp-content\/uploads\/2025\/07\/blogbild-EN-technologisches-onboarding-so-gelingts.png?w=990&amp;quality=78&amp;ssl=1 990w, https:\/\/i0.wp.com\/diselva.com\/wp-content\/uploads\/2025\/07\/blogbild-EN-technologisches-onboarding-so-gelingts.png?resize=768%2C621&amp;quality=78&amp;ssl=1 768w\" sizes=\"auto, (max-width: 990px) 100vw, 990px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">So what does that look like? If we start from<strong> the target image of a balanced team setup<\/strong> (onsite and remote\/nearshoring), then it would be as follows: <\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Tech\/Team Lead<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Why? The person in the tech lead role takes on <strong>responsibility and leadership<\/strong> and is therefore an existential <strong>link<\/strong>. A more in-depth technical training is necessary so that the person can <strong>represent<\/strong> these <strong>competencies<\/strong> at all. What should also not be underestimated: The tech lead should definitely be familiarized with the regional cultural customs of the onsite team so that this can also be passed on.   <\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Senior Developers<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Senior developers already have <strong>a great deal of technological knowledge<\/strong> and can therefore act perfectly as <strong>mentors for junior developers<\/strong> . Through early integration into code reviews, they can also be perfectly used to ensure and enforce <strong>code and project standards<\/strong> . This also leads to <strong>a relief for the tech lead,<\/strong> especially from a technical point of view.  &nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Junior Developers<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">An <strong>introductory workshop<\/strong> is to take place at the beginning. The goal is for all junior developers to be provided with their <strong>own mentors<\/strong> . This allows for <strong>gradual<\/strong> induction and also provides <strong>sufficient time<\/strong> for support. You will benefit enormously from the experience and knowledge of the senior developers.   &nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">QA Engineers and DevOps<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Once the <strong>basic system is up <\/strong>and running, it&#8217;s time to bring in the QA engineers and DevOps engineers. The nearshoring team now has enough specialist and project knowledge available and<strong> seamless integration <\/strong>into the development process can take place. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What else needs to be considered during technical onboarding?&nbsp;<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In addition to the correct order, there are of course <strong>other important points<\/strong>. The onsite and nearshoring team should have the <strong>same understanding<\/strong> and<strong> resources<\/strong> regarding the following topics: <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Technologies<\/strong> and <strong>frameworks<\/strong> used<\/li>\n\n\n\n<li>Documentation of the <strong>development environment<\/strong> (English!)<\/li>\n\n\n\n<li>Documentation of<strong> the required software, configurations and access data<\/strong><\/li>\n\n\n\n<li>Common <strong>code standards<\/strong> and establishment of regular <strong>code reviews<\/strong><\/li>\n\n\n\n<li>Joint <strong>debugging sessions<\/strong><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Now that the <strong>technology onboarding<\/strong> is running smoothly and the teams are equipped with the right tools, the next step is to address the <strong>cultural aspects<\/strong> as well. After all, nearshoring is not only about mastering the technology, but also about understanding how different cultures influence <strong>collaboration<\/strong> . In Belgrade, for example, <strong>Serbian culture<\/strong> plays a major role when it comes to team dynamics and way of working. In my next blog, I will therefore discuss the <strong>cultural peculiarities and influences<\/strong> in Belgrade and how these can influence everyday working life.   <\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Do you have any other additions?<\/strong> As already emphasized in my other blog post: <strong>Communication is key<\/strong>. Regular feedback, especially <strong>face-to-face<\/strong>, <strong>team building<\/strong> and <strong>mutual support<\/strong> are again the key to success. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">And of course: If support is needed with implementation or cultural integration, we are happy to provide our expertise. I am looking forward to your experiences and inputs! <\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a id=\"contact\" class=\"button is-dark\" href=\"mailto:hello@diselva.com\">Contact<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Effective technical onboarding for nearshoring teams: Tips for step-by-step integration, tools, code standards, and successful collaboration.<\/p>\n","protected":false},"author":268896782,"featured_media":111540,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_eb_attr":"","_crdt_document":"","advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1551,1554,1896,1916],"tags":[],"thema":[],"class_list":["post-97896","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-consulting","category-business-processes-levers-governance","category-establishing-nearshore","category-expert-article"],"blocksy_meta":[],"acf":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/diselva.com\/wp-content\/uploads\/2025\/09\/opengraph-diselva.png?fit=1200%2C630&quality=78&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/diselva.com\/en\/wp-json\/wp\/v2\/posts\/97896","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/diselva.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/diselva.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/diselva.com\/en\/wp-json\/wp\/v2\/users\/268896782"}],"replies":[{"embeddable":true,"href":"https:\/\/diselva.com\/en\/wp-json\/wp\/v2\/comments?post=97896"}],"version-history":[{"count":7,"href":"https:\/\/diselva.com\/en\/wp-json\/wp\/v2\/posts\/97896\/revisions"}],"predecessor-version":[{"id":113107,"href":"https:\/\/diselva.com\/en\/wp-json\/wp\/v2\/posts\/97896\/revisions\/113107"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/diselva.com\/en\/wp-json\/wp\/v2\/media\/111540"}],"wp:attachment":[{"href":"https:\/\/diselva.com\/en\/wp-json\/wp\/v2\/media?parent=97896"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/diselva.com\/en\/wp-json\/wp\/v2\/categories?post=97896"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/diselva.com\/en\/wp-json\/wp\/v2\/tags?post=97896"},{"taxonomy":"thema","embeddable":true,"href":"https:\/\/diselva.com\/en\/wp-json\/wp\/v2\/thema?post=97896"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}