WEBVTT

1
00:00:01.400 --> 00:00:03.403
A spreadsheet is not a strategy.

2
00:00:03.403 --> 00:00:11.855
Public financial management starts by naming the public result, the constraints, and the decision that financial evidence must support.

3
00:00:11.855 --> 00:00:20.119
Sharon Kioko and Justin Marlowe organize Financial Strategy for Public Managers around a practical claim: technique serves strategy.

4
00:00:20.119 --> 00:00:25.879
Forecasts, statements, ratios, cost models, and budgets matter because they improve choices.

5
00:00:25.879 --> 00:00:35.576
This episode adapts the book's overview, published by University of Washington Pressbooks under Creative Commons Attribution 4.0 except where otherwise noted.

6
00:00:35.576 --> 00:00:40.792
The narration condenses, paraphrases, and reorganizes the authors' explanatory prose.

7
00:00:40.792 --> 00:00:47.727
Separately credited cases, examples, figures, tables, photographs, quotations, and linked resources are excluded.

8
00:00:47.727 --> 00:00:51.168
Public organizations do not optimize a single bottom line.

9
00:00:51.168 --> 00:00:59.830
A city may need to preserve access, meet legal duties, maintain service quality, protect resilience, and use public money fairly at the same time.

10
00:00:59.830 --> 00:01:02.737
Financial analysis makes those tradeoffs visible.

11
00:01:02.737 --> 00:01:06.535
It cannot decide whose needs count or how risk should be shared.

12
00:01:06.535 --> 00:01:11.637
Those are governance choices, and the analysis should expose rather than conceal them.

13
00:01:11.637 --> 00:01:13.302
Begin with a decision statement.

14
00:01:13.302 --> 00:01:18.245
Name the service outcome, the people affected, the time horizon, and the authority responsible.

15
00:01:18.245 --> 00:01:25.270
Then distinguish recurring resources from one-time resources, controllable costs from obligations, and measured facts from assumptions.

16
00:01:25.270 --> 00:01:30.681
A projection should show a base case and credible alternatives instead of presenting one precise future.

17
00:01:30.681 --> 00:01:33.784
A useful recommendation connects mission and money.

18
00:01:33.784 --> 00:01:44.309
It explains what changes operationally, identifies cash and budget effects, tests sensitivity to uncertain inputs, and names what evidence would trigger a course correction.

19
00:01:44.309 --> 00:01:51.184
The same reasoning should be understandable to finance staff, program managers, elected officials, and residents.

20
00:01:51.184 --> 00:01:53.020
Torrance application segment.

21
00:01:53.020 --> 00:01:58.210
This original independent-study segment is separate from Kioko and Marlowe's book.

22
00:01:58.210 --> 00:02:12.008
It cites three City of Torrance primary-source pages checked October seventh, twenty twenty-six: Budget Documents at torrance C A dot gov slash Government slash Departments Offices slash Finance slash Budget Documents;

23
00:02:12.008 --> 00:02:15.933
Audit Reports at the same Finance section slash Audit Reports;

24
00:02:15.933 --> 00:02:21.819
and Transparent Torrance at torrance C A dot gov slash Government slash Transparent Torrance.

25
00:02:21.819 --> 00:02:30.104
For a hypothetical service proposal, begin with the adopted budget and current budget-review records to identify authority and planned resources.

26
00:02:30.104 --> 00:02:36.904
Use the annual comprehensive financial report listed on the Audit Reports page to establish audited historical context.

27
00:02:36.904 --> 00:02:43.932
Use the transparency page only as a route to current dashboards and tools, with each platform and reporting period labeled.

28
00:02:43.932 --> 00:02:49.017
Then state the proposed public result, alternatives, assumptions, and monitoring trigger.

29
00:02:49.017 --> 00:02:54.274
This workflow does not evaluate Torrance's financial condition or recommend a City decision.

30
00:02:54.274 --> 00:03:04.121
The discipline is repeatable: define the public purpose, assemble relevant evidence, compare feasible choices, explain distributional effects, decide, and monitor.

31
00:03:04.121 --> 00:03:09.376
Technical fluency supports accountability only when the public can follow the argument.

32
00:03:09.376 --> 00:03:16.965
This adaptation credits Sharon Kioko and Justin Marlowe and is licensed under Creative Commons Attribution 4.0.

33
00:03:16.965 --> 00:03:24.075
Changes include condensation, paraphrase, reorganization, and a separately sourced Torrance application.

34
00:03:24.075 --> 00:03:27.699
No author, publisher, or City endorsement is implied.