ICI su LinkedIn: Addetto IT https://lnkd.in/dsmcVUCm Responsabile di… (2024)

Project : ❌ Road Accident Analysis✅ Objective:Analyzed road accidents to provide valuable insights and mitigate incidents. Leveraged dummy data for a comprehensive study, focusing on different vehicles, surfaces, and weather conditions to enhance safety and support stakeholders.✅ Processes:Conducted thorough Data CleaningApplied Data Preprocessing techniquesUtilized Data Visualization for insightful presentationsPrimary KPIs:🔴 Total Casualties: Examined total casualties over two years🔴 Serious Casualties: Analyzed serious casualties for two years🔴 Slight Casualties: Investigated slight casualties over two years🔴 Casualties by Car: Explored casualties specifically involving cars over two years✅ Key Analytical Outputs:Presented total casualties by different vehicle typesConducted a year-over-year comparison to gauge the trend in accident numbersAnalyzed casualties based on different road types, surfaces, and areasExamined casualties in varying light conditionsDynamic Insights:The project's flexibility is demonstrated through the use of slicers for Accident Date and Locality Type (rural, urban), allowing real-time adjustments to the presented information.✅ Tools Used:ETL (Extract, Transform, Load) processesExcel for comprehensive data analysisPivot Tables for dynamic and interactive reportingThis project not only showcases technical skills in ETL and Excel but also highlights a commitment to road safety through data-driven decision-making.

3

To move from bad data to good data, you need a way to move from observability into action (in minutes, not months). You need Inspector. Inspector is your new, actionable data quality workflow. In a nutshell, Inspector lets you find, fix, and prevent data quality issues, before they impact your analytics. Get up to speed on Inspector’s workflow with the latest update from our CTO and Co-Founder, Sölvi 👉 https://lnkd.in/ecUFPvpy

13

9 commenti

"It's the driver’s fault". One of the most overly and improperly used phrases in the logistics industry. This was the centerpoint as the reason for a number of unreported accidents and damages to company resources. As a business analyst it is my job to be objective and look for the bread crumbs. You will need to delve deeper into problems and better understand what is truly happening.So, I took on this challenge to identify the issue(s) and explore this unique situation. When looking to analyze a business problem the first action can not be to throw money at the issue. You will need to get to the "root cause". One of my favorite tools/techniques is the Ishikawa diagram better known as "The Fish Bone Diagram".With the diagram and conducting interviews myself and the team were able to better understand business requirements, investigate company practices. We collectively were able to agree on what were the major underlying issues were.What did we learned:-The driver's were improperly trained or never received training at all.-Many were fatigued from being overworked.-The facilities infrastructure was inadequate to handle night time parking.-Driver's felt a sense of disloyalty from management. So in conclusion yes the driver's played a role but the bigger consensus was that there needed to be an updated business requirement documentation and documents and that multiple current procedures were inundated.

Six Sigma is different from other quality initiatives because its main focus is to improve customer value and efficiency, and ultimately enhance bottom line of the organization (Pyzdek, 2003).Read more 👉 https://lttr.ai/APXsG#AccountingServices #GreaterEfficiency

Customer support is a valuable part of Customer experience . ACPT analysis is a methodology for enhancing and attending to customer discontent and dissatisfaction.I have taken time to share some knowledge inspired by a mentor Akinyemi Oloruntoba Dada . Thanks to Kolapo Bankole for the support on the project.Don’t forget to leave your thoughts in the comments!!#speechanalytics #contactcenter #solutionarchitecture #dataanalytics

40

22 commenti

Are you passionate about process improvement and data analytics?Are you experienced in initiating and overseeing complex projects? We have 2 exciting Operations Specialist opportunities on our Baggage Operations and Facilitation teams! ✈ 📊 Click to find out more. 1) Baggage Operations: https://lnkd.in/gej-kti42) Facilitation: https://lnkd.in/gQzzaNYv#ProjectManagement #OperationsSpecialist #BaggageOperations #ProgramDesign #DataAnalystics #ProcessImprovement

13

Day 4 ☺️.Part 1.Vocabulary which are commonly used during customer audits. 客先監査に際して一般的に使用さえる語彙．1. 品質 (ひんしつ) - Quality - 例: 製品の品質を確認します。 (Seihin no hinshitsu o kakunin shimasu. - We will check the quality of the product.)2. 基準 (きじゅん) - Standard - 例: この基準に従って評価します。 (Kono kijun ni shitagatte hyouka shimasu. - We will evaluate according to this standard.)3. 監査 (かんさ) - Audit - 例: 来週、監査が行われます。 (Raishuu, kansa ga okonawaremasu. - The audit will be conducted next week.)4. 報告書 (ほうこくしょ) - Report - 例: 監査の報告書を作成します。 (Kansa no houkokusho o sakusei shimasu. - We will prepare the audit report.)5. 記録 (きろく) - Record - 例: 全ての記録を確認してください。 (Subete no kiroku o kakunin shite kudasai. - Please check all the records.)6. 不具合 (ふぐあい) - Defect - 例: 不具合が見つかりました。 (Fuguai ga mitsukarimashita. - A defect was found.)7. 是正 (ぜせい) - Correction - 例: 是正措置を講じる必要があります。 (Zesei sochi o koujiru hitsuyou ga arimasu. - Corrective actions need to be taken.)8. 点検 (てんけん) - Inspection - 例: 定期的な点検が必要です。 (Teikiteki na tenken ga hitsuyou desu. - Regular inspections are necessary.)9. 手順 (てじゅん) - Procedure - 例: 手順を遵守してください。 (Tejun o junshu shite kudasai. - Please follow the procedure.)10. 合格 (ごうかく) - Pass/Approval - 例: 全てのテストに合格しました。 (Subete no tesuto ni goukaku shimashita. - All tests were passed.)11. 基盤 (きばん) - Foundation - 例: 品質管理の基盤を強化します。 (Hinshitsu kanri no kiban o kyouka shimasu. - We will strengthen the foundation of quality management.)12. 管理 (かんり) - Management - 例: 在庫管理を徹底します。 (Zaiko kanri o tettei shimasu. - We will thoroughly manage inventory.)13. 確認 (かくにん) - Confirmation/Verification - 例: データの確認が必要です。 (Deeta no kakunin ga hitsuyou desu. - Data verification is necessary.)14. 改善 (かいぜん) - Improvement - 例: 継続的な改善を目指します。 (Keizokuteki na kaizen o mezashimasu. - We aim for continuous improvement.)15. 責任 (せきにん) - Responsibility - 例: 誰が責任者ですか？ (Dare ga sekininsha desu ka? - Who is the person responsible?)頑張りましょう🤗

5

Finalizando mais um curso “Customer Service: Problem-Solving and Troubleshooting”

6

🧮An easy way to calculate Customer Count is by taking every customer and checking if Revenue was > greater than 0.If Yes, then that Customer records a 1 for Customer Count in that month.Read more 👉 https://lttr.ai/AOeLQ#cfo #fpanda #fpandhey #careers

3

An interactive quality dashboard of advisor performance in an organisation...In this dashboard we have:1) Total Headcount, Audit Coverage, Total Audita, etc.2) Overall CQ Score3) We have Top Defects which is created in Pareto Chart.4) We have TL wise, Channel wise and Category wise CQ Score. In category, we have Star, Challenger and Care.5) We have Top Call Drivers.#dashboard #qualityanalyst #bpo #quality #qualitymanagement #pivottable #bposector #qualitydashboard