7P13SR- TWO- SHEET3&4

profileSa1_Jyyy
MN7P13SRModuleHandbookMar24.docx

Module Handbook

Module Title:

Building Business Insights

Module Code:

MN7P13

Module Leader:

Prof KOH Kee Lee

Dr. Bing Wong

Session: 2024/2025

Teaching period: Spring, March 2024

Pre-requisites: 120 credits gained at Level 7

Canvas URL: http://Stanfort.instructure.com

1. Teaching team

Details of staff teaching on the module

Name

Role

Office and office hours

Email

Prof. Koh Kee Lee

Dean, EDP

Level 11, Stanfort Academy

[email protected]

Dr Bing Wong

Senior Lecturer

Level 11, Stanfort Academy

[email protected]

2. Module Summary and Description

This module provides you with the opportunity to work on specific management and business issues that organisations are facing. Utilising your problem-solving skills and competences of handling and managing business challenges. Starting from problem identification and concluding with solution related recommendations, thus encouraging research into real world business and management issues impacting organisations.

Building Business Insights brings together the learning processes from the whole MBA programme. It encourages the synthesis of knowledge, theories and skills developed in the modules during the previous terms in order to provide realistic solutions to contemporary business and management challenges.

Module Aims

This applied module aims to allow students to:

· Integrate their prior knowledge into an in-depth investigation of specific management and business problem or issue and present the results

· Facilitate the identification of topical issues in the business/management area of interest

· Assimilate theories and concepts drawn from different areas and the wider business/management literature

· Develop and implement strategies in data collection, analysis, synthesis and in building compelling arguments

· Apply reflective practice, ensuring models and concepts can be used effectively in the critical evaluation of your performance.

· Synthesise knowledge, experience and reflective practice to continually develop professional skills and competences

Module Learning Outcomes

On successful completion of the module, students will be able to:

1. Demonstrate the different approaches to business/management issue(s) in the context of their chosen area to be investigated, with the use of appropriate evidence-based information and theory.

1. Discuss and critically evaluate the different perspectives of related evidence-based and theoretical literature including appropriate referencing from diverse sources.

1. Demonstrate acumen in the design, planning, selection and collection of evidence in investigating the chosen issue using primary and/or secondary data as deemed appropriate

1. Communicate effectively including your collection of evidence in the form of reports using appropriate formats in a well-structured report

1. Utilise reflective practice techniques to critique your performance and identify improvements.

1. Demonstrate the development of independent and self-managed learning

Learning Resources

Core Text

Conn C., McLean R., (2019) Bulletproof Problem Solving: The One Skill That Changes Everything, John Wiley & Son

Other Texts

In addition to the core text for this module, students will be expected to draw upon a wide range of knowledge from reading already undertaken throughout their programme and research contextual to their topic under investigation

Robson, C. (2016). Real World Research. 4th Ed, Chichester, John Wiley & Sons

Saunders, M., Lewis, P. & Thornhill, A. (2019) Research Methods for Business Students. 8th ed. Harlow: Pearson Education Limited

Pacer, W., (2019) Research Methods: Concepts and Connections, 2e, Worth Publishers

Journals

· Harvard Business Review

· Journal of Management Inquiry

· International Studies of Management and Organisation

· British Journal of Management

To pass the module you must achieve an overall minimum mark of 50%. If you pass the module on re-assessment, the component you resit will be capped at a pass mark level of 50%

7

6. Assessment

A portfolio made up of the following three components:

Component 1, AS1 - Business Insights Project Report (80% of module grade)

This report should take the style of a consultancy report, rather than an academic article, making extensive use of infographics and other visuals.

1. Definition of the problem (5%, 400 words):

· Describe the client for whom you are solving a problem, locating them within their industry. Identify the decision-maker within the client organisation who is the primary audience for your project report.

· A short description of the situation that prevails for your client at the outset of problem solving (i.e., the state of affairs that sets up the problem).

· A set of observations or complications around the situation that creates the tension or dynamic that captures the problem (i.e., what changed or what went wrong that created the problem), which should be fully evidenced via data from your client.

· In the form of an objective (e.g., to reclaim market share), define a specific and actionable problem (i.e., what are we trying to solve?).

· Identify any boundaries and constraints of the project, considering the key forces (e.g., values) acting on decision-makers.

· Identify the criteria against which successful resolution to the problem can be measured and judged.

NB: You should use your problem definition worksheet as a basis for this section, but should not present your problem definition worksheet.

2. Disaggregation of problem structure and solution drivers (25%, 2000 words):

· Use an initial logic tree (i.e., factor/lever/component) to break the problem into component parts or issues to illustrate and define the basic structure of the problem (e.g., causes of the problem).

· This should be evidence-based, using a combination of credible industry and academic literature, evidence and theory, covering the problem generally and the problem in the context of your client.

· Provide a fully-referenced commentary of the logic tree, concluding with a summary of the insights gained. It is expected that this logic tree will have three layers.

· Using the basic problem structure logic tree as a guide to locate further industry and academic literature, evidence and theory on the problem component parts of issues, produce a more complete logic tree (i.e., deductive logic or hypothesis) of the drivers of the problem solution, which help us to see potential pathways to solve the problem (e.g., hypothesised solutions).

· Provide a fully-referenced commentary of the logic tree, concluding with a summary of the insights gained. It is expected that this logic tree will have four layers.

3. Prioritisation of solution pathways (10%, 800 words):

· Using a prioritisation matrix, identify the potential pathways to solve the problem (e.g., hypothesised solutions).

· From the more complete logic tree, prioritise the ‘leaves’ that have the biggest impact on the project and which you can most affect to find the critical path to solving your problem, pruning the tree to remove the ‘leaves’ that are not on the critical path to solving the problem.

· Provide a fully-referenced commentary of the prioritisation matrix, concluding with a summary of the solution pathways (e.g., hypothesised solutions) that will be taken forward to be tested via analyses.

4. Workplan (10%, 800 words):

· Starting from the prioritised solution pathways (e.g., hypothesised solutions) of the more complete logic tree, describe the workplan by which you tested your solution pathways (e.g., hypothesised solutions) via analyses, so to be able to reach a conclusion on the solution to the problem.

· For each solution pathway identify the research questions that guided the testing of each solution pathway and, in a chunky workplan table, identify your hypothesised answers to your research questions, the data you used, how accessed or collected your data and the data analysis techniques you used.

5. Analysis and findings (30%, 2,400 words):

· Commence by presenting your ‘one day solution’ on the basis of your understanding ahead of your analysis, summarising the situation that prevails at the start of your project, the complication (i.e., what changed or what went wrong) and your current understanding of a resolution.

· The situation and complication may have evolved from original definition of the problem.

· Summarise what insights are still required to reach a solution, so to justify the forthcoming analysis.

· Sequentially working through each of your research questions, present the analysis you undertook and the findings. Wherever possible, visually present your findings (e.g., graphs, infographics).

· For each research question, clearly state the insights that have been gained.

NB: It is not required that you will need to undertake primary data collection (e.g., surveys, interviews, focus groups) or highly sophisticated analysis (e.g., regression modelling, thematic analysis), but you may feel these methods are critical to solve your problem. If so, discuss with your supervisor ahead of commencing such work.

6. Synthesised conclusions (20%, 1,600 words):

· Draw together the individual findings and insights of your problem-solving work into an overall picture.

· Using a pyramid structure, present your conclusions (i.e., governing thought) as an engaging story supported with arguments, findings, insights and facts to convince your audience of the merits of your recommended solution.

· Provide a commentary of your pyramid structure.

Word count: 8,000 words (excluding contents, figures, references and appendices).

Component 2, AS2 - Reflective Practice Report (10% of portfolio grade)

A report that reflects upon your learning journey in undertaking your business insights project covering the following:

1. The challenges you faced during the development of your Business Insights project

2. How you sought to overcome these challenges.

3. What you learned and how what you learned would manifest in doing something differently if faced with similar challenges again in the future.

Word count: 1,000 words (excluding references)

Component 3, AS3 - Reflective Practice video presentation (10% of portfolio grade)

A recorded video using slides that reflects upon your accomplishments and future needs covering the following:

1. How the submitted elements of the portfolio meet the module learning outcomes.

2. The relevance of the experience gained within this module to your future career aspirations.

3. Development needs to meet your future career aspirations that were not met on this module.

You should submit your slides along with a YouTube link to your video to the Turnitin folder.

Time limit: 10 minutes recorded

A step by step on how to create an Unlisted Video

UNLISTED VIDEO:

Private videos will not come up  in Google results,  YouTube results or your channel. 

Unlisted means your  video will not show  in any search results or your channel. Only those who know the link can watch the  video. You can share the link with anybody including those who are not  YouTube registered users.

YouTube, a social networking website, gives every Web surfer the opportunity to share their videos with a wide audience. If you run a small business, you can use YouTube to share product information, promotional videos and even training videos with anyone, anywhere in the world. In some cases, you might not want your videos to be quite so accessible, and you may decide to limit certain videos to a few employees or other users.

By default, YouTube makes every video you upload public; however, you can make a video unlisted and share it only with specific people who have the link to the video.

You can make a video unlisted when you upload it, or you can change a previously uploaded video to unlisted.

Make a Video Unlisted When Uploading

1. Navigate to the YouTube website and sign in to your account.

2. Click "Upload" at the top of the screen.

3. Click "Select Files From Your Computer" and select the video you want to upload. The video begins uploading automatically and the Video Options screen appears.

4. Click "Unlisted" and your choice will be applied to the video as it uploads. Give the YouTube link for the video (on the left side of the screen) to the people who are authorized to view the video.

Make a Video Unlisted After Uploading

1. Navigate to YouTube and sign in to your account.

2. Click your screen name in the upper right corner of the browser window. Click "Video Manager" from the drop-down menu.

3. Click "Edit" under the video that you want to make unlisted.

4. Click "Unlisted" and then click "Save Changes." Give the YouTube video link, which is located directly under the "Unlisted" button, to the people who are authorized to view the video.

All three components must be submitted.

Component 1, AS1 due on 30 September 2024

Component 2, AS2 due on 30 October 2024

Component 3, AS3 due on 30 November 2024

Supervision

You are expected to attend one-to-one meetings with your supervisor throughout the duration of the module, at the following points:

1. Start of the project: To review your submission from MN7027 Business Problem Solving and the feedback received and to agree initial work to be undertaken.

2. Definition of the problem: To review your completed draft of your definition of the problem section, identify required changes and agree next steps to be taken.

3. Disaggregation of problem structure and solution drivers: To review your completed draft of your disaggregation of problem structure and solution drivers section, identify required changes and agree next steps to be taken.

4. Prioritisation of solution pathways: To review your completed draft of your prioritisation of solution pathways section, identify required changes and agree next steps to be taken.

5. Workplan: To review your completed draft of your workplan section, identify required changes and agree next steps to be taken.

6. Analysis and findings: To review your completed draft of your analysis and findings section, identify required changes and agree next steps to be taken.

7. Synthesised conclusions: To review your completed draft of your synthesised conclusions section, identify required changes and agree next steps to be taken.

NB: It is the responsibility of the student to initiate each of these supervisory meetings. The student needs to send the supervisor a completed draft of each section, from which the supervisor will respond with a proposed meeting time to be agreed with the student.

8

Business Insights Report Grading Rubric

Definition of the problem (5%)

Disaggregation of problem structure and solution drivers (25%)

Prioritisation of solution pathways (10%)

Workplan (10%)

Analysis and findings (30%)

Synthesised conclusions (20%)

Distinction (70% plus)

A completely clear and succinct description of a complicated problem background.

A highly specific and actionable problem presented as an objective. A clearly bounded project with excellent awareness of the client’s needs. A highly specific and measurable success criteria.

Highly logical disaggregation of problem into components or issues, which provides excellent insight to the problem that was not available prior to disaggregation.

Disaggregation that is connected to and fully informed by both industry and academic literature.

Highly logically building upon the basic problem structure logic tree, a fully-evidenced and referenced more complete logic tree that substantially advances thinking on the problem towards drivers of the problem solution, identifying highly clear and practical pathways to solve the problem.

Exceptional analysis of solution drivers to objectively determine which will have the biggest impact on the problem and which can be actively managed. Highly logical pruning of ‘leaves’ of your final logic tree to establish a critical part to solving the problem.

Highly clear links between solution pathways, research questions, fact gathering and critical analysis. Highly clear procedure by which you will rigorously access data. Highly clear procedure by which you will rigorously analyse data. Highly appropriate selection of analysis tools to answer research questions.

A highly insightful ‘one day solution’ that clearly establishes the insights still required to solve the problem.

Having accessed highly valid data, highly rigorous execution of data analysis. Highly logical translation of findings into business insights that contribute to solving the problem.

Exceptional analysis to identify the critical findings and insights for solving the problem.

Exceptional synthesizing of critical findings and insights into an overall picture using the pyramid structure.

A governing thought completely supported by arguments, findings, insights and facts.

Merit (60%-69%)

A clear and succinct description of a complicated problem background.

A specific and actionable problem presented as an objective. A clearly bounded project with good awareness of the client’s needs. A specific and measurable success criteria.

Logical disaggregation of problem into components or issues, which provides good insight to the problem that was not available prior to disaggregation.

Disaggregation that is partly connected to and informed by both industry and academic literature.

Logically building upon the basic problem structure logic tree, a fully-evidenced and referenced more complete logic tree that substantially advances thinking on the problem towards drivers of the problem solution, identifying clear and practical pathways to solve the problem.

Very good analysis of solution drivers to objectively determine which will have the biggest impact on the problem and which can be actively managed. Logical pruning of ‘leaves’ of your final logic tree to establish a critical part to solving the problem.

Clear links between solution pathways, research questions, fact gathering and critical analysis. Clear procedure by which you will rigorously access data. Clear procedure by which you will rigorously analyse data. Appropriate selection of analysis tools to answer research questions.

An insightful ‘one day solution’ that clearly establishes the insights still required to solve the problem.

Having accessed valid data, rigorous execution of data analysis. Logical translation of findings into business insights that contribute to solving the problem.

Excellent analysis to identify the critical findings and insights for solving the problem.

Excellent synthesizing of critical findings and insights into an overall picture using the pyramid structure.

A governing thought supported by arguments, findings, insights and facts.

Pass (50%-59%)

Reasonable description of a problem background.

A problem presented as an objective. A bounded project with a success criteria.

Reasonable disaggregation of problem into components or issues, which provide some insight to the problem that was not available prior to disaggregation.

Disaggregation that attempts to connect to both industry and academic literature.

Logically building upon the basic problem structure logic tree, a fully-evidenced and referenced more complete logic tree that somewhat advances thinking on the problem towards drivers of the problem solution, identifying pathways to solve the problem.

Reasonable analysis of solution drivers to determine which will have the biggest impact on the problem and which can be actively managed, but with some errors. Pruning of ‘leaves’ of your final logic tree to establish a critical part to solving the problem, but with some errors.

Somewhat unclear links between solution pathways, research questions, fact gathering and critical analysis. Somewhat unclear procedure by which you will rigorously access data. Somewhat unclear procedure by which you will rigorously analyse data. Not selecting the most appropriate analysis tools to answer research questions.

A ‘one day solution’ that establishes the insights still required to solve the problem.

Having accessed data, execution of data analysis. Translation of findings into business insights that contribute to solving the problem.

Reasonable analysis to identify important findings and insights for solving the problem.

Reasonable synthesizing of critical findings and insights into an overall picture using the pyramid structure.

A governing thought not fully supported by arguments, findings, insights and facts.

Fail (49% and below)

An unclear description of a problem background.

A vague problem presented as an objective.

Disaggregation of problem into components or issues, but which provides no additional insight to the problem beyond what was available prior to disaggregation.

Use of irrelevant industry and academic literature

that do not drive problem solving.

Attempt to build upon the basic problem structure logic tree, an evidenced and referenced more complete logic tree but which does not meaningfully advance thinking on the problem towards drivers of the problem solution, establishing only unclear pathways to solve the problem.

Flawed analysis of solution drivers which fails to determine which will have the biggest impact on the problem and which can be actively managed. Flawed pruning of ‘leaves’ of your final logic tree, failing to establish a critical part to solving the problem.

Unclear links between solution pathways, research questions, fact gathering and critical analysis. Unclear procedure by which you will rigorously access data. Somewhat unclear procedure by which you will rigorously analyse data. Flawed selection of analysis tools that do not robustly answer research questions.

A ‘one day solution’ that does not clearly establish the insights still required to solve the problem.

Limited access to valid data with only superficial analysis. Business insights identified, but not based upon findings.

Flawed analysis to identify findings and insights for solving the problem.

Flawed synthesizing of critical findings and insights into an overall picture using the pyramid structure.

A governing thought not fully supported by arguments, findings, insights and facts.

8

image1.jpg