Tech debt is often unavoidable in most early stage startups. Not fixing the tech debt as a company gets traction and scales is more of a problem than the original creation of the tech debt. Turning a blind eye to tech debt has implications beyond the stack and creates an unstructured and sloppy culture.
Facilitating the interface between IT and business is data governance, which is filled with opportunity. There is no specific career path into data governance, but the ability to understand metadata and contextualize organizational insights to executives holds much opportunity.
Ist Business Intelligence ein Luxus? Daten – richtig gemacht – sind weder billig noch einfach. Die meisten Unternehmen warten, bis sie eine gewisse Größe erreicht haben, bevor sie in eine interne Datenkompetenz investieren. Ein Greenfield-Projekt, der erste Aufbau einer internen Datenfunktion, ist ein wichtiger erster Schritt auf dem Weg eines Unternehmens zur Datenreife. Vor der Einrichtung einer internen Datenfunktion kann ein Unternehmen als Daten unreif gelten, unabhängig davon, wer die Daten nutzt oder wie lange das Unternehmen bereits besteht.
Irinia Nikiforova explains what data governance is and why it is essential for any business that not only wants to survive, but use insights from data or data-driven products to drive growth.
The AI mystique might be the biggest obstacle to AI adoption. The artisanal data scientist who works on an alchemy of code output the magical algorithm impedes discussion on what is needed to commercialize and scale AI solutions. AI needs to be treated like a product and an item to be manufactured and scaled on an industrial level.
According to a D3M Labs poll, many data analysts who answered wanted to move into management, be it product management or people management. Behind the desired career move, was the interest to step back from the keyboard and focus on the communication and greater involvement in business and strategy.
Technical debt in your data pipeline will impact your organization in ways that will annoy stakeholders, make the working lives of analysts tedious and frustrate data engineers. This debt can cause embarrassment in front of boards and investors, as numbers can be mismatching and unexplainable. And worse.
Data teams are often chaotic places to work, which leads to attrition, over hiring, burn-out and other bad side effects. Stevan Lazic, an experienced product engineering leader who has worked at numerous startups and scaleups, talks with Elizabeth Press about what he thinks is driving the unhealthy dynamic in many data teams and what measures can be taken so that data teams are properly resourced.
Matt Brady, Founder of Zuma Recruiting and I talked about Data Strategy. We will start by covering data strategy and roadmaps before discussing how to treat data, data roles and where data should sit in an organization. Data teams add the best value to their organization when they are part of a holistic company strategy discussion and work as strategic partners with the stakeholders.
The major challenges to AI implementation are often mind-set based rather than technical. Problems in production and implementation of AI often stem from organizations‘ and practitioners‘ lack of ability and/or desire to thoroughly scope out and define the problem they are trying to solve. Consequently, they often don’t select the right tools, capabilities and processes to implement successfully. Organizations can also negelct operations (such as MLOps), which are important for work efficacy and scale.
