Working Outside the Microsoft Stack

Send us a textWelcome to the Clearly Podcast. The podcast is taking a break for a few weeks due to another project, and upon return, there will be exciting news. Today's discussion revisits what it takes to be a Power BI consultant, focusing on the necessary skills and qualities.Experience with Power BI is valuable, but not mandatory for juniors. Key qualities include consulting skills, analytics, business experience, understanding data, and articulating it clearly. Being able to work with senior people to address business processes is also essential.For those fresh out of college or university, it's important to have a grasp of business fundamentals and good Q&A skills. Graduates often have skills in algorithms and data science. Conversing with business users to understand their challenges and developing solutions is crucial.The role of a Power BI consultant now often includes elements of data engineering, data warehousing, or machine learning. It’s important to have a broader knowledge of the data landscape. Employers should seek a mix of skills rather than expertise in every area.For someone starting, understanding data engineering and data modeling is key. Learning to build models that others can use and gaining experience in visualizing data is important. Download Power BI, use public datasets, and practice.Knowing how to find information about connectors for other applications is crucial. Being able to get back to clients with accurate information is essential.During interviews, honesty about skills is important. People often claim more experience than they have. Private projects show initiative and learning and should not be dismissed.There is high demand for roles, especially for those who understand the entire Microsoft stack. Consultants should keep their knowledge up to date through communities, podcasts, and continual learning.For aspiring consultants, working on side projects and learning new skills is beneficial. Employers appreciate self-starters who take initiative.The podcast will return with exciting news after the break. Thank you for listening and stay tuned for more insights.You can download Power BI Desktop from here. If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here. To find out more about our services and the help we can offer, contact us at one of the websites below: UK and Europe: https://www.clearlycloudy.co.uk/ North America: https://clearlysolutions.net/

Send us a textThe podcast discusses the current state of the IT consulting job market, particularly focusing on skills and opportunities in 2024. The conversation highlights the end of the post-COVID job market boom, noting that recruitment has slowed, with hiring managers delaying decisions and tighter budgets. However, there are signs of recovery with an increase in RFPs.The job market trend is similar in both the UK and the US, though the US is slightly better off, with contractors getting renewed more frequently. During the post-COVID boom, even mediocre candidates demanded high salaries, which is no longer sustainable. Now, candidates need to upskill and be proactive.Skills in high demand include pre-sales capabilities, combining product knowledge with the ability to confidently present to clients. Soft skills are emphasized as being equally important as technical skills. Companies are increasingly requiring employees to be in the office, at least part-time, to enhance learning and integration, especially for new employees. The hybrid work model is becoming more common, balancing office and remote work.Job seekers are advised to be proactive by updating their CVs, tailoring them for each job, and engaging directly with employers and recruiters. Side projects and continuous learning can help candidates stand out.There is growing demand for AI skills, but AI will not replace human roles entirely. It enhances human capabilities, and the best candidates will continue to improve and adapt. The importance of validating and understanding AI outputs, especially in critical fields, is highlighted.The podcast concludes with a suggestion to make this job market update a regular segment to keep the audience informed.

Send us a textWelcome to the Clearly Podcast. After some light-hearted banter about annual leave and running shoes, the discussion shifts to the main topic: Azure vs. Fabric.The conversation covers the components of Azure and Fabric, focusing on Power BI, Azure Data Factory (ADF), OneLake, and Synapse Analytics. Fabric offers better integration and cost control for users who need multiple components. However, for those using a single component like ADF, the benefits of migrating to Fabric are less clear.From a customer perspective, streamlining licencing and management is a significant advantage of Fabric. Azure requires separate licences for each component, while Fabric consolidates this into a single licence. This can simplify administration and reduce costs, especially for future expansions.For on-premise customers considering a move to the cloud, the best approach might be a gradual shift. First, migrate to Azure components, then transition to Fabric. This incremental strategy minimizes service interruptions and spreads out the rearchitecture workload.There are also scenarios where sticking with Azure might be more practical. If an organization primarily uses components like ADF for non-analytical purposes, the complexity of managing Fabric could outweigh the benefits. The consensus is that while Fabric offers significant advantages for data analytics, Azure components will continue to cater to other use cases, and there is no immediate push for all customers to move to Fabric.In summary, customers should evaluate their specific needs, considering both immediate and future use cases, to decide between Azure and Fabric. The transition should be planned carefully, leveraging Azure as a stepping stone when moving from on-premise environments.

Send us a textWelcome to the Clearly Podcast, where today's discussion focuses on Power Apps, particularly canvas apps, model-driven apps, and Power Pages, and how to choose the right one.Power Pages are ideal for external, infrequent users due to their pricing model and ability to handle large user bases. In contrast, canvas and model-driven apps are more suited for internal use. Canvas apps offer high customization and a user-friendly mobile interface, making them great for tasks like inventory logging. However, they require careful management to avoid becoming overly complex. Model-driven apps, which are form-based and linked to Microsoft CRM, are faster to set up and better for structured, transactional tasks but are limited to using Dataverse.Client discussions typically start by identifying the project’s goals, budget, and timeline, prioritizing essential features, and planning additional phases. Managing expectations is crucial to prevent overcomplicating the project.When choosing data sources for canvas apps, Dataverse is preferred, but budget constraints might lead to using SharePoint lists, which must be managed carefully to avoid data issues. Deciding on data storage upfront is essential to avoid complications later.Power Pages are low-code environments suitable for creating external portals without needing individual licenses, making them ideal for customer portals. They support both authenticated and unauthenticated users and are priced based on usage.Clients often start using Power Apps by transitioning from cumbersome Excel spreadsheets to improve data management and security. Demonstrating practical examples helps clients understand the benefits.Long-term care and maintenance of Power Apps involve planning for support, ensuring sufficient storage, and considering future improvements. A support plan can be more cost-effective than hiring full-time staff and ensures ongoing maintenance.Power Apps are an investment requiring ongoing care and development. Thank you for joining the discussion, and we look forward to the next episode.

Send us a textIn this episode of the Clearly Podcast, the hosts discuss data quality dashboards. These dashboards monitor data entry to flag errors and ensure data accuracy, especially in systems with significant human input. Key points include:Definition and Use: Data quality dashboards highlight data entry errors, allowing for prompt correction. Errors disappear from the report once fixed, providing satisfaction to users.Routine Recommendation: These dashboards are essential, particularly where user input is high.Risks of Poor Data Quality: Inaccurate data can lead to flawed reports and decisions. Regular monitoring helps maintain data integrity.Application Redesign: Dashboards can reveal systematic issues, sometimes leading to application redesigns. Simplifying the interface or automating processes can prevent errors.Building the Dashboard: Start by identifying key issues through stakeholder discussions. Focus on major errors first, like dates and large transactions. Decide whether to automate error resolution or require manual approval.Senior Management Buy-In: Effective communication ensures the dashboard is seen as a tool for improvement, not punishment. This promotes user engagement and data quality.Continuous Improvement: If errors persist, it may indicate a deeper application issue requiring broader solutions.The hosts emphasize the importance of data quality dashboards in maintaining accurate data, which is crucial for reliable reporting and decision-making.

Send us a textHosts: Andy Clark, Tom GoughGuest: Greg Bounds Topic: Dealing With a Mess of Data Systems and ProductsKey Points:1. Introduction:·      Andy and Tom introduce Greg Bounds, who works as a data architect for a national nonprofit and also consults on data projects.2. Defining the Problem:·      The discussion focuses on inheriting a complex data environment, termed a "dog's breakfast," with a mix of applications, systems, and databases.·      Tom emphasizes the challenges of dealing with multiple cloud providers and on-premises systems.3. Scoping the problem:·      Start by talking to various stakeholders to understand the importance of different systems.·      Auditing and documenting the systems should follow naturally from these conversations.4. Managing Stakeholder Priorities:·      Understand the challenge of balancing different departments' priorities and stresses the importance of understanding the entire data flow.·      Show the benefits of changes through small, manageable projects.5. Technical Approach:·      Look for low-hanging fruit and opportunities to consolidate systems for quick wins.·      Simplifying the data architecture can de-risk the environment and reduce points of failure.6. Benefits of Consolidation:·      Understand there may not be immediate cost savings, reducing the number of platforms simplifies governance and management.·      It also minimizes the need for specialized knowledge across multiple systems.7. Planning for the Long Term:·      The importance of data governance and having a data team that is approachable and open to new solutions.·      Ensuring the data team has the right skills and capacity is crucial to maintaining a streamlined environment.8. Key Takeaways:·      Communication with stakeholders and understanding their needs is essential.·      Focus on data quality and transparency, even if it means creating "snitch reports" to highlight issues.·      Look for quick wins to build momentum and show the value of changes.·      Engage the C-suite to drive adoption and support across the organization. You can download Power BI Desktop from here. If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here. To find out more about our services and the help we can offer, contact us at one of the websites below: UK and Europe: https://www.clearlycloudy.co.uk/ North America: https://clearlysolutions.net/

Send us a textThis week, Andy, Tom, and Shailan, discuss the challenges and considerations of working with technologies outside the Microsoft stack from a consulting perspective.Key Points:Encountering Non-Microsoft Technologies:·      Clients often use various non-Microsoft technologies like Google Analytics, Salesforce, Oracle, etc.·      Consultants must be prepared to handle data sources and systems outside the Microsoft ecosystem.Balancing Expertise and External Help:·      Evaluate whether to learn new technologies internally or bring in external experts.·      Consider the long-term strategic value of learning a new technology versus the immediate need for expertise.Cost and Time Considerations: ·      Training and rework can be costly and time-consuming when working with technologies outside your skill-set.·      It's often more efficient to hire experienced consultants for niche technologies to avoid mistakes and reduce implementation time.Deciding When to Say No:·      Assess if a project aligns with your core expertise and strategic goals.·      Avoid taking on projects that significantly deviate from your primary skill set to maintain focus and reputation.Strategic Partnerships:·      Partnering with vendors can provide necessary training and support.·      Ensure the vendor has good implementation skills, not just product knowledge.Pricing and Client Communication:·      Factor in the cost of external resources when pricing for clients.·      Have honest conversations with clients about the costs and impacts of using niche technologies.Opportunity Costs:·      Taking on projects outside your expertise can lead to missed opportunities in your core area.·      Focus on projects that align with your business direction and offer better margins.Project Selection:·      Deliberately choose projects that help expand your expertise in desired areas, like broader Power Platform work.·      Avoid projects that don't align with your strategic aims, even if they seem lucrative.Conclusion:Navigating non-Microsoft technologies requires a balance between internal learning and external expertise, clear communication with clients, and strategic project selection to maintain focus and deliver quality results.You can download Power BI Desktop from here. If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here. To find out more about our services and the help we can offer, contact us at one of the websites below: UK and Europe: https://www.clearlycloudy.co.uk/ North America: https://clearlysolutions.net/

Send us a textIn this episode of the Clearly Podcast, the hosts discuss how to choose a cloud provider. They emphasize starting with the big three providers: Azure, AWS, and Google Cloud Platform, as these offer comprehensive services, long-term stability, and a large pool of skilled professionals. It's generally unrealistic to consider other niche platforms unless you have very specific needs tied to a particular vendor's products.When evaluating cloud providers, consider what you're trying to achieve and the specific services offered by each platform. It's essential to evaluate all options objectively and avoid defaulting to a familiar vendor without proper assessment. Consultants can help organizations maintain a neutral stance and make informed decisions based on current needs, costs, and skill sets.The hosts also address the issue of personal biases in technology decisions and stress the importance of making choices based on solid evidence rather than emotions. They note that switching cloud providers, while challenging, is not impossible and can be managed more efficiently with lessons learned from initial implementations.Negotiation with cloud vendors is possible, especially for larger enterprises, and it's beneficial to work with partners to secure the best deals. Finally, they advise leaving biases at the door and making decisions that are well-justified and based on thorough evaluation.You can download Power BI Desktop from here. If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here. To find out more about our services and the help we can offer, contact us at one of the websites below: UK and Europe: https://www.clearlycloudy.co.uk/ North America: https://clearlysolutions.net/

Send us a textWelcome to the Clearly Podcast. This episode kicks off the new season with a discussion on transitioning organizations away from the Excel mindset. Excel is widely used for storing and managing data, but it’s not a structured tool and can lead to significant challenges in data projects.Excel’s flexibility makes it easy for quick mock-ups and data input, but these solutions often lack consideration for data structure, security, and quality. Relying on Excel can also hinder scalability and precision, leading to issues like broken reports and security vulnerabilities.The conversation highlights the need for a cultural shift within organizations, driven by top-down support. It's important to educate teams on the limitations of Excel and demonstrate the benefits of more advanced tools like Power BI, Power Apps, and structured databases. These tools offer better data management, security, and efficiency, freeing up time for more valuable tasks.Despite the challenges, transitioning away from Excel is possible with the right approach. This includes clear communication of the benefits, managing expectations, and ensuring buy-in from senior leadership. While Excel can still play a part in data management, the goal is to use it in conjunction with more advanced solutions to achieve better overall data literacy and efficiency.In summary, the podcast emphasizes the importance of moving beyond Excel to more structured data solutions, highlighting the benefits and strategies to achieve this transition within organizations.You can download Power BI Desktop from here. If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here. To find out more about our services and the help we can offer, contact us at one of the websites below: UK and Europe: https://www.clearlycloudy.co.uk/ North America: https://clearlysolutions.net/

Send us a textIn this episode of the Clearly Podcast, we discuss the concept of democratizing data within organizations. The key points covered in the conversation include:Definition and Critique: The term "democratization of data" refers to making data accessible to a wider group within an organization. The hosts critique the term, suggesting it often sounds like marketing jargon meant to sell software licenses.Traditional Data Access: Historically, data access has been siloed within departments such as accounts or sales. The idea behind democratization is to break down these silos and allow broader access to data.Challenges and Risks: Several challenges come with democratizing data, including data security, proper cataloging, and understanding the data. There are risks of data leaks and the complexity of managing access across different systems.Self-Service and Citizen Developers: The conversation touches on the issue of self-service BI and citizen developers. While empowering users to create their own reports and handle data sounds appealing, it can be distracting from their primary roles and is often more complicated than anticipated.Action Plan for Democratization: To achieve democratization effectively, organizations should start with improving data literacy. Employees should understand what data means, how to handle it responsibly, and the implications of data misuse.Governance: Implementing proper governance is crucial. This involves identifying key questions that need answers, determining the necessary data sources, and applying security measures. A phased approach is recommended to gradually expand access. Final Thoughts: The discussion emphasizes the importance of starting small and ensuring that everyone in the organization understands the data they are working with before rolling out broader data access initiatives. Overall, the episode highlights the complexities and considerations involved in democratizing data, urging a thoughtful and phased approach to implementation.You can download Power BI Desktop from here. If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here. To find out more about our services and the help we can offer, contact us at one of the websites below: UK and Europe: https://www.clearlycloudy.co.uk/ North America: https://clearlysolutions.net/